WAS or LDAP as an external source
3 answers
If you configure WAS with LDAP and Jazz with LDAP you can use the Import users feature to import users that qualify in LDAP. Search the help for 'import' to find the help topic. There is also a Synchronize LDAP feature in repotools. Please search the help for 'Synchronize LDAP'.
I am ot sure what happens if you configure WAS with a local realm. With Tomcat the local realm is writable. Therefore you can create the users in JTS and they are created in the tomcat-users.xml.
Comments
OK, that helps Elek.
We have 10 users in WAS, and "Import Users" in the Manage Users section of Jazz is greyed out. So I seem to have to create the users in WAS AND in Jazz...which is silly. However, since we have customers without LDAP, we have to make a decision on what to do.
Oddly, I created 4 or the 10 WAS users in Jazz, and it was great that their Groups migrated over. To our surprise, the other 6 could STILL log in to jazz!!, Their names appeared as ADMIN/ADMIN and email ADMIN. (Defect?)
Ah ah ... now you are facing the special rule... :)
Here is how it works 1) the user attempts to log in WAS...userid/password are validated.... 2) then we fetch the group associated to that user JazzAdmin, JazzUser etc etc 3) then we send the group and userid to Jazz 4) Jazz checks the userid
if (userid.exist) then allow else if group==JazzAdmin AND jazzAdminProperty=true then user.becomeJazzAdmin()
So your 6 users should be JazzAdmin AND youhave the property com.ibm.team.repository.ws.allow.admin.access=true in teamserver.properties
Does it match what you have ?
One specific example that they might not, you can only synchronize from the current LDAP server configured in Jazz Adv Properties, if you have multiple LDAP servers you must change your configuration between syncs. Even if you have federated registry in WAS across them and they can all login, the sync jobs can only be pointing at one directory at a time.
-Sean
Comments
Hi,
Have you steps on what you need to do please?
I presume you change it "on the fly" to point at the relevant ldap import users etc?
How is does authentication work?
You have two LDAP servers, Bluepages one, and TDS one.
They are configured as federated in WAS.
JTS points at BP and works currently.
How do I import from TDS, and allow BOTH sets of users to sign in without issues?
Thanks
Mark,
In my prior company (~10,000 employees) we synched users every night.. added to LDAP, they got added to the Jazz Users group, and given a Stakeholder license (using pooled licenses. We didn't TELL the users they were added, just did it.
and when a user left the company, we archived them in Jazz..
this way you don't have all that import/license confusion everytime someone sends them a link to a workitem they should look at or comment on.
if you needed some different license/group, then u submitted a service ticket and got added to the right place