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.

Sign up for GitHub

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

Jump to bottom

Authorization path and token path different #313

Open
piyush0609 opened this issue Sep 13, 2016 · 2 comments
Open

Authorization path and token path different #313

piyush0609 opened this issue Sep 13, 2016 · 2 comments

Comments

@piyush0609
Copy link

How to tackle this issue when authorization path and token path are different for an API.
@nrempel
Copy link

nrempel commented Nov 10, 2016

I have the same issue. Would a pull request be accepted if I were to implement a solution?

I propose allowing authorizePath to be passed as a full url. If that is the case, then use the url instead of appending authorizePath to baseSite.

What do you think @ciaranj?

@samsullivan samsullivan mentioned this issue Jan 11, 2018
Open
@samsullivan
Copy link

@piyush0609 I opened #341 based off of @nrempel's suggestion after running into the same issue with Facebook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nrempel @samsullivan @piyush0609