-
Notifications
You must be signed in to change notification settings - Fork 11.8k
feat: sync federated users from LDAP #35718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: dc2b23e The changes in this PR will be included in the next version bump. This PR includes changesets to release 37 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #35718 +/- ##
===========================================
- Coverage 59.62% 59.62% -0.01%
===========================================
Files 2832 2832
Lines 68352 68356 +4
Branches 15138 15155 +17
===========================================
Hits 40754 40754
- Misses 24992 24995 +3
- Partials 2606 2607 +1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from federation code perspective
Co-authored-by: Debdut Chakraborty <[email protected]>
Proposed changes (including videos or screenshots)
This PR allows pre-registering federated users through the LDAP sync process, by loading the federation domain name from an LDAP attribute. If the specified attribute is missing or equal to the workspace's Home Server, the user will be created as a local user; If it's a different value, then the user will be created as a federated user.
With this, it's possible to display the display name and other profile information about remote users even before anyone talks to them using federation.
The federation domain will only be loaded on user creation. If an user is created as local, it can't be changed to a remote user. If it's a remote user, it can't be changed to local nor can its domain be changed.
Issue(s)
CORE-1072
Steps to test or reproduce
Further comments