Multiple LDAP servers

We have a "Forest" set up, I.e. we have multiple Trees (Domains) that create a Forest.

RTC connects to the Forest, not individual domains.

That is how we cope with multiple domains. There is one provision, a user in the "Forest" has to be unique, so you cannot have the same user ID on more than one domain/tree.

Not sure if this helps,

Jas

Internal users of RTC are placed in a different LDAP server than external users. Is it possible to configure RTC with two LDAP servers so that RTC is searching in both?

Has anyone done this? If yes what are the pre-conditions? Same structure, same kind of LDAP server ect?

Thanks in advance,
Elisabeth

Hello Elisabeth,
it could be a use case for
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/86967
no?

Eric.

ehodel a crit :

Internal users of RTC are placed in a different LDAP server than
external users. Is it possible to configure RTC with two LDAP servers
so that RTC is searching in both?

Has anyone done this? If yes what are the pre-conditions? Same
structure, same kind of LDAP server ect?

Thanks in advance,
Elisabeth

Thanks Jason and Eric for your answers.

Elisabeth

We have a "Forest" set up, I.e. we have multiple Trees (Domains) that create a Forest.

RTC connects to the Forest, not individual domains.

That is how we cope with multiple domains. There is one provision, a user in the "Forest" has to be unique, so you cannot have the same user ID on more than one domain/tree.

Not sure if this helps,

Jas

Jas, could you, please, provide some more details about your solution? Does that mean that you succeeded in setting up RTC to connect to 2 different base DNs? We are about to solve similar situation and this would be very helpful.

Thanks in advance,
Jan

In our environment we need to connect to 2 different LDAP.

I need to connect to one Active Directory "Forest" for internal users and to another forest with external users.

Is it possible to connect RTC into 2 different "forests"?

Thanks a lot and best regards.

Wagner Arnaut

We have a "Forest" set up, I.e. we have multiple Trees (Domains) that create a Forest.

RTC connects to the Forest, not individual domains.

That is how we cope with multiple domains. There is one provision, a user in the "Forest" has to be unique, so you cannot have the same user ID on more than one domain/tree.

Not sure if this helps,

Jas

Jas, could you, please, provide some more details about your solution? Does that mean that you succeeded in setting up RTC to connect to 2 different base DNs? We are about to solve similar situation and this would be very helpful.

Thanks in advance,
Jan

Is there a solution for this?

We are using RTC 3.0.1 with WAS7 and LDAP/AD.

My issue is we are migrating from one domain to another. e.g. current LDAP server is hsc.ad.gov.ca and the new LDAP server will be ontario.ad.gov.ca, and all users are migrating from OU=Extended Desktop Users,OU=SAS,OU=CFCS,DC=hsc,DC=ad,DC=gov,DC=on,DC=ca
to OU=Extended Desktop Users,OU=SAS,OU=CFCS,OU=CYSSC-Legacy,DC=Ontario,DC=ad,DC=gov,DC=on,DC=ca

Since the user migration will be done in waves, so I am looking at if RTC can support connecting to two LDAP servers at the same time. Can I ask LDAP admins to create a forest like what you guys have? Otherwise I will just ask them to put all RTC users in the same wave and we just switch over (I just need to change some LDAP parameters in WAS and RTC, I suppose).

Thanks
Jirong

Internal users of RTC are placed in a different LDAP server than external users. Is it possible to configure RTC with two LDAP servers so that RTC is searching in both?

Has anyone done this? If yes what are the pre-conditions? Same structure, same kind of LDAP server ect?

Thanks in advance,
Elisabeth

If you are using WAS, you can do this (don't know about Tomcat), by setting up Federated realms. There is an article in the library which describes this. The one restriction of this is that when importing a new user, you had to change the RTC LDAP config (not the WAS config), so that RTC could find the user. This is because RTC itself does not recognise multiple LDAPS, as does WAS (this was with RTC2, not sure about RTC3). So it does work, but is a bit fiddly.

In the end we went with the Forest approach mentioned below, a lot simpler. Interestingly enough, when I was dealing with IBM support, and pointed them to the RTC article on Federated realms, they suggested to stay away from this, and go with the Forest approach if possible!