Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

LDAP integration - email not present

I've configured the LDAP authentication of my jazz server (Standard edition 2.0) following the documentation instructions.
I'm now able to import user from LDAP and I'm able to login with them.
Unfortunately, on my LDAP, there isn't the user email information.
On this situation the LDAP nightly sync task show me some warnings regarding the user with empty email field and is not able to import the new users added to jazz groups.
Is there the possibility to populate this field in other mode during the LDAP nightly sync task?
Or is there the possibility to exclude the check on email field?

Thanks in advance.

0 votes



7 answers

Permanent link
Opened WI https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/90933 to address this issue.

--- Balaji

I've configured the LDAP authentication of my jazz server (Standard edition 2.0) following the documentation instructions.
I'm now able to import user from LDAP and I'm able to login with them.
Unfortunately, on my LDAP, there isn't the user email information.
On this situation the LDAP nightly sync task show me some warnings regarding the user with empty email field and is not able to import the new users added to jazz groups.
Is there the possibility to populate this field in other mode during the LDAP nightly sync task?
Or is there the possibility to exclude the check on email field?

Thanks in advance.

0 votes


Permanent link
Added support for performing nightly sync without email address. If email address is not present in LDAP, perform the following steps to manage name, user id and group membership in LDAP (email will be managed by Jazz repository).

1. Run Repotools -syncUsers to sync the users in LDAP with Jazz repo (This is a on-demand sync tool to synchronize users with ldap...similar to the nightly sync task that runs at 1AM every day)

2. Run repotools -exportUsers to export the list of users in a csv file.

3. Fix the email address value in the csv file.

4. Run repotools -importUser fromFile=users.csv to update the email addres value of the users

Now the users email address field is present in the Jazz repository. Subsequent nightly sync will NOT null out the email address field.

--- Balaji
Jazz Server Team



Opened WI https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/90933 to address this issue.

--- Balaji

I've configured the LDAP authentication of my jazz server (Standard edition 2.0) following the documentation instructions.
I'm now able to import user from LDAP and I'm able to login with them.
Unfortunately, on my LDAP, there isn't the user email information.
On this situation the LDAP nightly sync task show me some warnings regarding the user with empty email field and is not able to import the new users added to jazz groups.
Is there the possibility to populate this field in other mode during the LDAP nightly sync task?
Or is there the possibility to exclude the check on email field?

Thanks in advance.

0 votes


Permanent link
Good to know this!!!

One of my projects have 100 users and 12 of them show email address 'unknown'. I have worked with Rational Support for 2 weeks and was told there is no workaround.

After export and modify the csv file, may I delete the entries that are good and only import back what I want to fix? I think this may have less impact to the repository. Any comment? Thanks.

0 votes


Permanent link
One more question - does this approach work for RQM1.0.1.1?

0 votes


Permanent link
Yes, you can delete the entries that are good and import the entries that need to be fixed.

Even if you don't delete it, it will skip those entries because the data to be imported is same as the user information present in the repository.

--- Balaji

One more question - does this approach work for RQM1.0.1.1?

0 votes


Permanent link
Thanks, Balaji.

Is this available in RQM2.0 or RQM1.0.1.1? I had a quick test last Friday, but got errors like https://localhost:9443 is not acessible. I'm not using "localhost" to access RQM web, not using port 9443 (I use 443 instead).

0 votes


Permanent link
I added this feature (skip email address if not present in LDAP) in Foundation 1.0.0.1.

RTC 2.0.0.1 is based on Foundation 1.0.0.1. So, the feature will be available in RTC 2.0.0.1.

I am not sure about RQM releases. Maybe someone from RQM team can answer it. I would hope RQM 2.0.0.1 is based on RTC 2.0.0.1 builds.

--- Balaji






Thanks, Balaji.

Is this available in RQM2.0 or RQM1.0.1.1? I had a quick test last Friday, but got errors like https://localhost:9443 is not acessible. I'm not using "localhost" to access RQM web, not using port 9443 (I use 443 instead).

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Aug 21 '09, 10:37 a.m.

Question was seen: 8,197 times

Last updated: Aug 21 '09, 10:37 a.m.

Confirmation Cancel Confirm