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.

Sign up for GitHub

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

Jump to bottom

Rename bypass values for better clarity #13

Closed

aeneasr opened this issue Nov 3, 2017 · 0 comments

Member

aeneasr commented Nov 3, 2017

The options are a bit confusing:

BypassAuthorization: Basically a passthrough - does not modify the access token at all
BypassAccessControlPolicies: Requires an access token with an appropriate scope but does not check access control policies - injects a JWT as bearer token
AllowAnonymous: If an access token is supplied, it is introspected for the user. If that fails, or no token was given, the user is called anonymous - injects a JWT as bearer token

aeneasr pushed a commit that referenced this issue


          Renames bypass values for better clarity

a22d2be

Closes #13
Closes #29

aeneasr mentioned this issue

Renames bypass values for better clarity #31

Merged

aeneasr closed this as completed in #31

aeneasr pushed a commit that referenced this issue


          Renames bypass values for better clarity

46a717e

Closes #13
Closes #29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment