CC RTC Synchronization fails: case sensitive username?
Simon Eickel (1.1k●7●54●57)
| asked Jul 30 '13, 8:45 a.m.
retagged Aug 12 '13, 11:06 a.m. by Ralph Earle (257●3●9)
Hi there,
I'm facing the error, that the synchronizer fails because there is some kind of login case sensitivity. Is there any possibility to prevent the synchronizer to fail? Or ... other question ... is there any possibility to get this matched? When I log into jazz.net he takes a special case, e.g. upper case, even when typing the username in lower case. This seems to be something like the user is created in AD ... Greetings, Simon |
2 answers
In Jazz, on the advanced properties page, you have the UseCaseSensitiveUsernameMatching property.
This needs to match the case sensitivity setting of your LDAP (or whatever you use). It seems that you are using case insensitive matching, and the user is stored in LDAP as uppercase, hence, this is what is sent to the synchronizer. The case in which you type the username when logging in is not relevant, as the username is not forwarded directly from your login form to the synchronizer. Comments 1
Hi simon,
Simon Eickel
commented Jul 31 '13, 1:05 a.m.
Hi Piotr,
Simon Eickel
commented Jul 31 '13, 1:05 a.m.
Hi Abraham,
|
Hi Simon,
Can you simply change the synchronization user ID to the upper case, and resync? This page may help you figure out how to change the user ID: https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.team.connector.scm.cc.doc/topics/t_sync_edit_stream.html Comments
Simon Eickel
commented Jul 31 '13, 3:41 a.m.
Hi Masabumi,
Simon Eickel
commented Jul 31 '13, 3:41 a.m.
Even when changing the "ClearCase Login Name" of the ClearCase Provider Properties it doesn't change the "ClearCase User ID" of the Details screen (first snipped).
Oh, apologies I wasn't clear enough. I meant to change the synchronization user ID on the Team Concert tab of the Synchronized Stream editor. You probably have already changed it from the Properties panel, anyway.
Hi Masabumi,
|
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.