-
Notifications
You must be signed in to change notification settings - Fork 39
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
Couple of things not working as expected #111
Comments
Yes, this is wrong. Thanks!
Relative urls follow the same rules browsers do. So if
Thanks! Will also fix this |
I'm saying the ultimate URL I needed was
where
if I set my server URL to
I would have expected this:
to yield But I think I also see what you're saying, where:
which is not what I would have expected but, yeah, makes sense. Then again, with a trailing slash:
it yields what I was expecting but the way |
Yes, the confusion makes sense but this is indeed by design and also how (for example) the HTML |
jk, this worked with the trailing slash:
|
Yes! I would write this as:
But it's identical to prefixing with |
Cheers, thanks for helping me work through it! |
I'm using
authorization_code
grant, and got it working like so:From the README:
I'm not sure why this suggests not using the
clientSecret
. I needed it for it to work.From the types:
I couldn't get relative URLs to work, and looking here, I think these need to be
./
instead of/
.This would also explain why I needed to specify
tokenEndpoint
at all, since the default should have worked.From the README:
/** * You are responsible for implementing this function. * it's purpose is to supply the 'initial' oauth2 token. */ getNewToken: async () => { // Example return client.clientCredentials(); // Another example - return client.authorizationCode({ code: '..', redirectUri: '..', });
This needed to be
client.authorizationCode.getToken()
.The text was updated successfully, but these errors were encountered: