Remote-Name header returns capitalized uid instead of LDAP cn — cn attribute never fetched - #1072
Conversation
…cn attribute never fetched
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughLDAP lookups now retrieve the LDAP ChangesLDAP Directory Name Propagation
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant AuthService
participant LDAPService
participant ContextMiddleware
participant UserController
LDAPService-->>AuthService: Return dn, email, cn
AuthService->>ContextMiddleware: Provide UserSearch.Name
ContextMiddleware->>ContextMiddleware: Select directory name or capitalized username
ContextMiddleware-->>UserController: Provide authenticated user context
UserController->>UserController: Set session name when Name is available
Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
Add "cn" to LDAP GetUserInfo attributes, propagate it through UserSearch.Name, and use it instead of Capitalize(username) when setting the LDAP user's display name in basicAuth, cookieAuth, and session creation
Found via automated repo scanning, fix written and reviewed before opening.
Summary by CodeRabbit