| << Back to previous view |
|
[QB-1928] Add a mechanism to sync user information from LDAP SIDE BASED ON GROUP NAME
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Vartika Paul | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | All environments | ||
| Description |
|
When we actually create a group with the same name in Quickbuild as the LDAP Group... Quickbuild performs a match between the users which are present in quickbuild to the users which are a part of the Active directory (The LDAP Group) and work accordingly for sending notifications etc...
To make it little more simple .. PROBLEM : Problem 1 : A new QUICKBUILD GROUP (with the same name as the LDAP Group(PDL)) was created -> All the Users of the new group will have access and will get notifications from quickbuild if users have earlier logged on to quickbuild and they exist in quickbuild Problem 2: The LDAP GROUP (PDL) Admin modifies the LDAP GROUP (removes/adds new users) -> Quickbuild will only pick up the user level changes if the user logs into quickbuild after the modification to the LDAP Group is being made ..or someone has to manually remove the users ISSUE: In Quickbuild, when a LDAP Mapped group is used as a Notification target.. the user group relation is only queried from LDAP and when user logs into QB ..this should not be the case... FEATURE REQUESTED: To add a mechanism to sync user information from LDAP side based on group name, which is quite different rom current mechanism of synching group information based on user name. |