Re: What's the best way to set up LDAP in ITM

So if you don't have the above-mentioned userid restriction or future need
for SSO, and thus could choose either the hub or TEPS-based LDAP
authentication, then I would say go with the hub TEMS LDAP auth.  In my
experience, it has worked more smoothly and flexibly than the TEPS-side's
LDAP authentication setup.  Not to mention, I believe the VMM code (handles
federated repository cases) underneath eWAS's covers still might have
problems with multiple prinicples being returned.  Could be wrong there of
course as it may have been addressed in a fix, but I believe it's working
as designed in the case that two identical userid's are returned from
distinct repositories.

Toben


On Mon, Jan 21, 2013 at 3:27 PM, Julius Loman <[email protected]> wrote:

> On Mon, Jan 21, 2013 at 02:37:32PM -0600, Gregory Mendes <
> [email protected]> wrote:
> >
> > Through the TEPS or Hub_TEMS? What's the best practice and things to
> consider? Regards,
> If your user id's are shorter than 10 characters and you don't need the
> Single
> Sign On into TEPS, go for HUB TEMS LDAP authentication.
>
> If your user ID's are longer, you __need__ to use TEPS for LDAP auth. But
> SOAP
> requests and tacmd commands will not be LDAP authenticated in this case.
>
> I guess you can use combination of both TEPS and HUB TEMS LDAP
> authentication
> with some tuning. Anyway the 10 charater username limit still applies for
> anyone
> authenticating against HUB TEMS (SOAP/tacmd).
>
> --
>
> [ Julius Loman ][ [email protected] ][ http://lomo.kyberia.net ][
> icq:35732873 ]
>
>
> _______________________________________________
> TME10 mailing list
> [email protected]
> Unsubscribe:[email protected]
>
>


-- 
"Sometimes I think that's the only right thing to do:
To dream. to live in the world of dreams.
But it doesn't last forever--wakefulness always comes to take me back..."

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]