You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.
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.
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
The text was updated successfully, but these errors were encountered: