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

Refresh Token in a different URL #75

Closed
dccarmo opened this issue Apr 8, 2016 · 3 comments
Closed

Refresh Token in a different URL #75

dccarmo opened this issue Apr 8, 2016 · 3 comments

Comments

@dccarmo
Copy link

dccarmo commented Apr 8, 2016

So I'm currently working with an API that have a different endpoint for token refresh. How can I let Heimdallr know the refresh token URL (and maybe even allow the application to set parameters)?

@bckr
Copy link
Contributor

bckr commented Apr 18, 2016

Heimdallr does not support setting a different endpoint for the token refresh. To my knowledge it would be very unusual to define a separate endpoint just for refreshing the token. From the RFC:

The token endpoint is used by the client to obtain an access token by
presenting its authorization grant or refresh token. The token
endpoint is used with every authorization grant except for the
implicit grant type (since an access token is issued directly).

Out of curiosity: Is there a special reason why the API defines a separate endpoint for the refresh?

@dccarmo
Copy link
Author

dccarmo commented Apr 19, 2016

There isn't, actually. I talked to the back-end team and they admitted that their API wasn't following OAuth specs, so they updated and now everything is good. Sorry for not coming back to report this.

@dccarmo dccarmo closed this as completed Apr 19, 2016
@bckr
Copy link
Contributor

bckr commented Apr 20, 2016

Cool! Glad it worked out for you 👍

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

2 participants