migrating from federated repository to standalone LDAP repository
Hello,
Please can some one suggest me what points should I look into before migrating from federated to LDAP for authentication. This server is currently used for version control and we have a total of 20 users on this server.
RTC server details: RTC4x, Database: DB2, App server:websphere
What prerequisite do I need to perform before switching to LDAP.
Thanks
Ritesh Maurya
2 answers
Hello Ritesh,
you should be aware that the users are stored in the jts/ccm repository. When you switch to LDAP you should make sure that the users in LDAP have the same IDs as the users in the federated repository. During the configuration of LDAP you will map a LDAP attribute to the RTC user id. The ldap value of this attribute should be the same as the User ID in the JTS repository. If this is not the case you would get duplicated users during the synchronization between LDAP and JTS.
/Elisabeth
you should be aware that the users are stored in the jts/ccm repository. When you switch to LDAP you should make sure that the users in LDAP have the same IDs as the users in the federated repository. During the configuration of LDAP you will map a LDAP attribute to the RTC user id. The ldap value of this attribute should be the same as the User ID in the JTS repository. If this is not the case you would get duplicated users during the synchronization between LDAP and JTS.
/Elisabeth
When you say "federated repository", I suppose you refer to the built-in file-based repository. In this case, instead of "migrating", you can actually just add an LDAP connection to the existing federated repository - see the "hybrid LDAP & file based realm" section in the below article.
https://jazz.net/library/article/604
No matter what you do, as Elisabeth suggested, always keep the user IDs unique and consistent.
https://jazz.net/library/article/604
No matter what you do, as Elisabeth suggested, always keep the user IDs unique and consistent.
Comments
