| << Back to previous view |
|
[QB-637] User groups that do not exist in LDAP are reset after his login
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexey Shumkin | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: |
QB server - Windows 2003 Server R2, DB - Mysql
QB client - Windows XP SP2 |
||
| Description |
|
Assume QBA - QB root user which is created in the very beginning
Login under QBA Create two QB groups: Admins & Develop (such names do not exist in Active Directory (AD)) Create AD user <user-developer> with LDAP authenticator. Include <user-developer> into that two groups created above. Logout and login under <user-developer>. He has no any permissions Logout and login back under QBA. See <user-developer>`s groups - they are reset (there are no any) It`s confusing I guess it is incorrect behaviour. Manually set groups have not to be reset. Not all the times AD groups and users are the same as at the build server |
| Comments |
| Comment by Robin Shen [ 23/Sep/10 09:55 AM ] |
| This is by design. Otherwise, QuickBuild can not distinguish this case with the case when user is removed from certain groups at LDAP side. |
| Comment by Alexey Shumkin [ 01/Oct/10 04:09 PM ] |
|
I've got what I've done wrong! :))
I set "Search groups using filter" in LDAP authenticator settings But the option I need is "Do not retreive groups" |