Skip to content
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

Consider having introspection endpoint members strictly enforced #381

Open
MartinFlores751 opened this issue Dec 3, 2024 · 0 comments
Open

Consider having introspection endpoint members strictly enforced #381

MartinFlores751 opened this issue Dec 3, 2024 · 0 comments
Assignees
@MartinFlores751
Labels
enhancement New feature or request
Milestone
0.6.0

Comments

@MartinFlores751
Copy link
Contributor

Similar to #375.

See the "OAuth 2.0 Token Introspection" for reference: https://www.rfc-editor.org/rfc/rfc7662.html

We should consider having the following to allow for strict checking:

{
  "openid_connect": {
    "require_members_from_introspection_endpoint": ["aud", "exp", "iat", "iss", "nbf"],
  }
}

require_members_from_introspection_endpoint would be an enum in the schema, and contain the standard members found in "OAuth 2.0 Token Introspection".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MartinFlores751 MartinFlores751

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.6.0
Development

No branches or pull requests
1 participant
@MartinFlores751