Replies: 1 comment 5 replies
-
Hi, those ACLs for client is meant for admins of Meiling Gatekeeper (owner of the oAuth2 server) to control available scopes that can be authorized in specified client. You can think OAuth2ClientACL as following: In short, Adding a scope on client acl will enable the client to create token with the scope mentioned above. If the requested auth has scope that is not allowed in ACL, meiling will simply decline generating token/authorization code since that scope is not allowed for the client. |
Beta Was this translation helpful? Give feedback.
-
If I understand correctly if the client has ACL for a given group, the user who wants scopes will be checked under the point of being in the given group and are scopes available for the group? Is it the same with ACL users in the client? ( the user who wants scopes will be checked for presence in the client in the users ACL and if scopes are allowed for the given user? )
If possible, I would ask for a detailed explanation of how the ACL works in Meiling Gatekeeper,
Regards, RutsuKun
Beta Was this translation helpful? Give feedback.
All reactions