-
Notifications
You must be signed in to change notification settings - Fork 75
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.
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
Api protection JWt token introspection enhancement #410
Comments
Exception cases tested;
Evidence: |
Successful TestingTested code with successful Jwks validation of external IDP (access token generated other than underlying auth server) |
RSA and EC token testing results |
Code deployed and working as expected on gasmyr.gluu.org |
Requirement:
3) JWT Flow: -
3.1) Parse Jwt token
3.2) Validate Token - Issuer should be present in the restricted list
3.3) Validate Issuer
3.4) Retrieve Auth Server JSON Web Keys - jwks_uri"
3.5) Verify the signature used to sign the access token
3.6) Verify the scopes
If any of the above steps fails will throw 401 - Unauthorized.
4.1) If Issuer is present in any of above cases then it be validated against the restricted list and if issuer is not among this list than config-api reject’s call and will throw 401 - Unauthorized.
4.2) Issuer if present in restricted list than introspection url fetched using discovery endpoint and token validated against it.
4.3) If issuer is not present then the token will be validated against the underlying jans-auth-server.
Acceptance Criteria.
The text was updated successfully, but these errors were encountered: