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.

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

Customize Token Introspection response #1194

Closed
nhosoya opened this issue Jan 28, 2019 · 2 comments
Closed

Customize Token Introspection response #1194

nhosoya opened this issue Jan 28, 2019 · 2 comments
Assignees
Milestone

Comments

@nhosoya
Copy link
Contributor

nhosoya commented Jan 28, 2019

Feature

A configurable option to customize Token Introspection Response

Why?

There are members that are not implemented, but are defined as OPTIONAL by rfc7662 section-2.2. ( sub, username, and so on )
We want to return these values to our clients.

# 2.2. Introspection Response
def success_response
{
active: true,
scope: @token.scopes_string,
client_id: @token.try(:application).try(:uid),
token_type: @token.token_type,
exp: @token.expires_at.to_i,
iat: @token.created_at.to_i
}
end

@nbulaj
Copy link
Member

nbulaj commented Jan 31, 2019

Hi @nhosoya . Introduced with #1195 and will be released with next version of the gem

@nbulaj nbulaj closed this as completed Jan 31, 2019
@nbulaj nbulaj self-assigned this Jan 31, 2019
@nbulaj nbulaj added this to the 5.1 milestone Jan 31, 2019
@nhosoya
Copy link
Contributor Author

nhosoya commented Feb 1, 2019

Thanks for your quick works! 😺 @nbulaj

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

No branches or pull requests

2 participants