| << Back to previous view |
|
[QB-184] Default Groups assigment failed with LDAP authenticators
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christophe Lallement | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: |
Redhat AS4 Tomcat 5.5 java 1.5 maven 2.0.4 |
||
| File Attachments: |
QB_screenshots.zip
|
| Description |
|
I use an LDAP authenticators with user and group search. I have configured this authenticator with default groups to anonymous and group startegy to "add" The binding to the ldap server works fine. no specific group are availble inot the ldap directory. But when a user try to connect to quickbuild, no default group is available into his profile ? it means the use can see nothing. I should be "anonymous" I'm not sure but i believe it works fine with relese 1.1.5 Christope |
| Comments |
| Comment by Robin Shen [ 02/Jan/07 06:11 PM ] |
|
Christope, The default group only applies to newly created user in QuickBuild. For the user who does not get the default group, can you make below tests: 1. Delete the user from QuickBuild users administration page. 2. Login to QuickBuild with the user account you've just deleted. 3. After login, the user should be created in QuickBuild, please check to see if the default group is assigned to the newly created user. Regards. Robin |
| Comment by Christophe Lallement [ 03/Jan/07 03:47 AM ] |
|
Hi Robin I have already test this scenarii without succes i also have make a "Clear User Cache" before the login find as attachment screen capture to see if something is wrong. Regards Christophe |
| Comment by Robin Shen [ 03/Jan/07 08:16 PM ] |
|
This is a bug. A work around is to leave the "group name" property as blank when you configure the LDAP authenticator, and the default group should be associated with newly created user. This bug will be addressed in release 1.2.0 which will be available soon. Thanks. Robin |