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 Jul 3, 2020. It is now read-only.
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.
On Mon, Jun 5, 2017 at 9:23 AM, Yong Wen Chua ***@***.***> 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
<#38 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACiTR5z3aK2zkJ97d1LRPkx6wQVQAYuSks5sA1h0gaJpZM4NuDcD>
.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: