[SERVER-77855] Record specific warning if unable to re-acquire user authorization rights via LDAP Created: 06/Jun/23 Updated: 29/Oct/23 Resolved: 26/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Adrian Gonzalez Montemayor |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Security
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2023-09-18, Security 2023-10-02 | ||||
| Participants: | |||||
| Description |
|
Record when stale LDAP records are re-used in the AuthorizationSession. The AuthorizationSession is responsible for re-acquiring authorization rights, if it finds that its locally cached copy is stale. Various errors can be emitted during this re-acquisition process, and the AuthorizationSession must handle them. When an LDAP fault occurs during handle refresh, we should record a unique error message, and explain that we're falling back to stale information. We should write a test which validates that this message is emitted. |
| Comments |
| Comment by Githook User [ 25/Sep/23 ] |
|
Author: {'name': 'Adrian Gonzalez', 'email': 'adriangonzalezmontemayor@gmail.com', 'username': 'adriangzz'}Message: |