[closed] LDAP Integration with multiple LDAP DN's (mulitple AD Forests) with Jazz V.6.0 and later
Guido Schneider (3.4k●14●91●115)
| asked Sep 08 '15, 10:05 a.m.
closed Nov 10 '16, 3:07 a.m. by Ralph Schoon (63.6k●3●36●46) Hello All, I have a question about the LDAP integration with Jazz. We have the issue that our company will introduce a second AD forest with user accounts in it. This means we will have two LDAP registries with different base DN’s. In Jazz 5.0.2 is it (as much as I know) not possible to define two different LDAP registries with different DN's, user account and server to verify usernam/password in multiple DN’s. (btw. ClearQuest can do this). WAS itself could do this with federated repository, but the login is done in Jazz (Java-EE) and not in WAS. WAS does the access group resolution and the groups for the user import, if I’m correct. My Idea is now, (we have Jazz 6.0) to introduce JAS (Jazz Authorization Server), based on WAS liberty profile. And there it should be possible to define multiple LDAP registries with different DN’s etc.. I read through this documents:
Does anybody know if this idea is correct and the approach could work?
Following applications must work
Any technotes/infos/recommendations with this? Has anybody experience with JAS?
many thanks
|
The question has been closed for the following reason: "The question is answered, right answer was accepted" by rschoon Nov 10 '16, 3:07 a.m.
Accepted answer
I cannot comment on the JAS part as I have not actually done it yet, but I would like to clarify the WAS federated repository bit. With this configuration, the authentication (login) is done by WAS, and it assigns the repository role as well - in fact, it's always done by the application server (WAS or Tomcat). This means that as long as you configure multiple LDAP servers in WAS correctly, following the instructions in the below article, CLM should work without any issues.
https://jazz.net/library/article/604 The challenge is still user synchronization as you can configure the LDAP server in JTS only one at a time. Guido Schneider selected this answer as the correct answer
Comments
Guido Schneider
commented Sep 21 '15, 3:10 p.m.
Hello Donald, thank you for the answer.
I tried now this setup with a federated repository pointing to two AD Domains.
Result:
- for users of one domain all is working perfect
- user of other domain can login in Jazz but they get authorization failure. No member of repository groups
BUT: when I look the user in JTS/CCM/QM/RM admin page user management, he is member of the repository group e.g. JazzUsers. The checkbox is checked and grayed out.
So it looks for me like the App is doing somthing different on runtime privilege evaluation than on user management.
The user synch is not important yet for me. First the logins must work.
Any idea what? Do you know how this group evaluation is done n runtime?
Donald Nong
commented Sep 21 '15, 8:27 p.m.
CLM applications do not interact with the external user registry directly. The repository role assignment should be done during the authentication by the application server. With the user logged in, use the URL /<app>/authenticated/identity to verify this. For example, the URL https://jazz.net/jazz/authenticated/identity shows the privileges on jazz.net, and mine is {Double check the J2EE role mapping settings of the application in WAS if in doubt. 1
Hi Guido,
This part works now, but not with DomainLocal Groups. It Needs Universal Groups in Active Directory.
Now I have to evaluate a solution for user Import and update. I stll hope JTS sees JAS as a single repository and only JAS neds to know about two repositories.
Thanks Guido
Guido Schneider
commented Sep 24 '15, 3:52 p.m.
Additional comment: the group membership checkboxes shown in the user profile page within jazz admin, are showing the group membership evaluation done by the settings in advanced properties and not the real group membership done by the WAS application group mapping. This was confusing me so I searched long time on wrong end. I have this now up and running. Users of any LDAP registries can logon and use Jazz.
Only open issue is managing the users, because autoimport and manual import are only searching in the LDAP registry defined in Jazz advanced properties.
I'm now playing with self registration.
Any idea about update of existing users? Do we have to script this externally?
Do you know any plans to enhance Jazz so it can connect to multiple registries?
Regards
Guido
Mathieu Defianas
commented Nov 09 '16, 7:47 a.m.
Hello,
Donald Nong
commented Nov 09 '16, 7:43 p.m.
You should use LDAP and one of the LDAP servers in JTS. This is caveat when using WAS federated user repository to host multiple LDAP servers. For more details, check this article.
Mathieu Defianas
commented Nov 10 '16, 2:24 a.m.
Thanks @dnong.
showing 5 of 9
show 4 more comments
|