Open xkjyeah opened 7 years ago
The scope
parameter is not meant for specific use with LDAP. It was meant for specifying the resources that the user intends to access with the token. I'll see how I can do this in another manner.
True... that's hacking around the scope.
However it's similar to how Auth0 does it: https://auth0.com/docs/scopes/current
On Mon, Jun 5, 2017 at 9:23 AM, Yong Wen Chua notifications@github.com wrote:
The scope parameter is not meant for specific use with LDAP. It was meant for specifying the resources that the user intends to access with the token. I'll see how I can do this in another manner.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lawliet89/rowdy/issues/38#issuecomment-306082041, or mute the thread https://github.com/notifications/unsubscribe-auth/ACiTR5z3aK2zkJ97d1LRPkx6wQVQAYuSks5sA1h0gaJpZM4NuDcD .
Here's a sample of the fields available:
If the user specifies
scope=userPrincipalName,memberOf,mail
, the JSON web token should also include the following fields:This way, we can perform group checks without hitting the LDAP server
Relevant line of code: https://github.com/lawliet89/rowdy/blob/master/src/auth/ldap.rs#L101