Skip to content
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.

Adding option for configuring IntrospectionEndpoint #161

Open
amit-g opened this issue Sep 11, 2017 · 0 comments
Open

Adding option for configuring IntrospectionEndpoint #161

amit-g opened this issue Sep 11, 2017 · 0 comments

Comments

@amit-g
Copy link

amit-g commented Sep 11, 2017

IntrospectionEndpointTokenProvider currently uses /connect/introspect as introspection endpoint which works perfectly with IdentityServer. Some other provides (e.g. Okta - see link below) have slightly different endpoint but currently there is no option to configure it. Is there a reason for not providing this as configuration option? We have updated the IdentityServerOAuthBearerAuthenticationOptions.cs to add an option for IntrospectionEndpointPath which is by default "connect/introspect". That works for us. Does it make sense to include it in the main repository? The same thing applies to ValidationEndpointTokenProvider as well which has connect/accesstokenvalidation as path with no option to configure.

https://developer.okta.com/docs/api/resources/oidc.html#introspection-request

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

No branches or pull requests

1 participant