Summary: | Some Reviews may not be loaded | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
Component: | Mylyn | Assignee: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P1 | CC: | lmcbout, sebastien.dubois |
Version: | unspecified | ||
Target Milestone: | 0.9 | ||
Hardware: | PC | ||
OS: | Windows Vista | ||
Whiteboard: |
Description
Alvaro Sanchez-Leon
2011-11-09 16:31:31 EST
Something additional to consider. If ldap is configured and operational, the R4E preferences shall use it to populated the default user id and e-mail. So the userid is aligned. (In reply to comment #1) > Something additional to consider. > If ldap is configured and operational, the R4E preferences shall use it to > populated the default user id and e-mail. So the userid is aligned. That is already the case and it should work fine. Let me know otherwise We are now case-insensitive for participants and user Ids A protection has been implemented so if a user file at group level already exists for a new user, a new file is created with a consequtive number e.g. "_1" appended after the user id. This scenario would happen if e.g. the new user has the same id of an existing one but with a different case combination e.g. EEIABCD and eeiABCD However in order to simplify the internal handling and prevent multiple entries for the same user, the UI has been modified to allow user id entries in lower case only. see Bug 363838. |