You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2023. It is now read-only.
In webinterface (Admin --> Users --> ) there is an option to allow a user to be :
Admin ( Designates whether this user can perform administrative functions. )
Superuser ( Designates whether this user has all permissions without explicitly assigning them. )
By using mapping from Sentry ( 'owner', 'admin', 'manager', 'member') and LDAP groups, I have successfully integrated this functionality - so, a new user, as a member of a proper group in LDAP, is assigned a proper Sentry role.
But, users who are Owners and/or Admins don't have Admin and/or Superuser 'ticked' (turned on). So basically, a new member has a role of Owner or Admin, but he is not allowed in the Admin section.
Is it possible to assign this based on LDAP group membership (or any other parameter)?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In webinterface (Admin --> Users --> ) there is an option to allow a user to be :
By using mapping from Sentry ( 'owner', 'admin', 'manager', 'member') and LDAP groups, I have successfully integrated this functionality - so, a new user, as a member of a proper group in LDAP, is assigned a proper Sentry role.
But, users who are Owners and/or Admins don't have Admin and/or Superuser 'ticked' (turned on). So basically, a new member has a role of Owner or Admin, but he is not allowed in the Admin section.
Is it possible to assign this based on LDAP group membership (or any other parameter)?
The text was updated successfully, but these errors were encountered: