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

OAuth 2. 0 RFC 7662 introspect endpoint exists but is not "documented" #686

Closed
n2ygk opened this issue Aug 29, 2016 · 7 comments
Closed
Assignees

Comments

@n2ygk
Copy link

n2ygk commented Aug 29, 2016

Please make sure to document the RFC 7662 OAuth2 token introspection endpoint URL. See via the web console Identity Providers/Resident Identity Provider/Inbound Authentication Configuration/OAuth2/OpenID Connect Configuration the introspection endpoint URL is not shown, but it exists and works just fine (in 5.3.0):

Identity Provider Entity Id:    https://localhost:9443/oauth2/token
Authorization Endpoint URL: https://localhost:9443/oauth2/authorize
Token Endpoint URL: https://localhost:9443/oauth2/token
Token Revocation Endpoint URL:  https://localhost:9443/oauth2/revoke
User Info Endpoint URL: https://localhost:9443/oauth2/userinfo

Thanks!

@holgrs
Copy link

holgrs commented Oct 26, 2016

What is the Url of the introspection endpoint?

@n2ygk
Copy link
Author

n2ygk commented Oct 26, 2016

/oauth2/introspect

@chrisdrobison
Copy link

You might also want to document the discovery endpoint as well since that is supposed to exist.

@madurangasiriwardena
Copy link
Member

madurangasiriwardena commented Nov 7, 2016

Hi @n2ygk and @chrisdrobison ,

Thanks for pointing out the documentation issues.

At the moment we are at the development stage of IS 5.3.0 and these are new features added to IS 5.3.0. We are in the process of modifying the doc space the with new features. These features will be added to the documentation soon.

Thanks.

@Flickster42490
Copy link

Hi @madurangasiriwardena ,

I'm trying to hit the oauth2/introspect endpoint using an ajax POST call from the client, I get back a 401 unauthorized OPTIONS error. But when I directly make an options call using a tool like POSTMAN with a basic authentication header, it returns for me. Any idea why this might be happening and is it a documented issue?

Thanks.

@mefarazath
Copy link
Contributor

mefarazath commented Apr 6, 2017

You need to add CORS headers to server response to be able to do this using ajax. Similar discussion can be found here.

This blog discusses a solution for this on WSO2 Identity Server.

@mefarazath
Copy link
Contributor

Documentation related to introspection have been added https://docs.wso2.com/display/IS530/Invoke+the+OAuth+Introspection+Endpoint

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

No branches or pull requests

8 participants