-
Notifications
You must be signed in to change notification settings - Fork 139
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
Feature request: System role mapping #1174
Comments
Any comment or progress on this? Like I mentioned, it is a standard feature in LDAP authetication, so when transfering from LDAP->OIDC, you lose an important functionality that people are used to. |
This is a solid request — but why limit it to LDAP databases? It would make sense to map a |
Hi @audrieMSFT I see you have been assigned to this, do you think there will be progress? :) |
Hi @kkiiskin, I can understand how LDAP does it - all manager or course creator users can be put into separate contexts. How do you have it done in your case? Are they put into different groups? In that case, is the request to assign system context roles to users from configured groups? Regards, |
Hi @weilai-irl having managers/course creators in specified M365 group would propably be the most convenient way, yes. |
1 more vote to this. Having to assign roles manually is not ideal. |
In LDAP plugin settings there is a possibility to map certain LDAP contexts to system roles like Manager and Course Creator.
Could this be implemented in Azure AD integration too? For example based on O365 groups or user attributes.
The text was updated successfully, but these errors were encountered: