-
Notifications
You must be signed in to change notification settings - Fork 112
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 callback isn't called #59
Comments
U shoul use the provided token to make the authenticated requests |
Isn't this token supposed to be passed to my server via the callback? All I'm getting is page, show to the user, with the token. The callback isn't being called. |
I bet u r right. This is as far as i got too. |
@sblaz Do your commits work or just WIP? Would love to see a PR for this. Currently stuck here ourselves. |
I believe so, yes, although I was planning on doing a bit more testing before submitting a pull request. I was able to successfully authenticate with an OAuthSwift client after applying this and a couple of other patches - I'm not sure what happens if you just try to apply this one by itself. It's pretty simple, though, if you look at it, the oauth_callback parameter wasn't getting saved along with the other request token stuff. |
@sblaz Yup -- does look like that. Currently using your master branch -- removes the restrictive wp_http_validate_url looks like. |
Yes, that's right - I started by applying #33 but then wanted to use a custom url scheme so relaxed the validation further. Also had some issues with double-encoding of the oauth_callback parameter value. Applied #65 and then removed the two rawurlencode() calls in join_with_equals_sign() and it seems to be copacetic. |
Those changes got it working for me with OAuthSwift. |
In my case, normalize_parameters() is really messing up my already partially encoded parameters, so by removing normalize_parameters() instead, I was able to keep the rawurldecode() calls. See: #91 @sblaz , I have created a PR which merges your changes with AlexC's and removes normalize_parameters() in favor of encoding them in the join_with_equals_sign() function: #92 Thanks! |
I tried to setup a callback but it's never called. The oauth documentation says that I must provide
oauth_callback
parameters but I get an error saying that the callback is missing. It works if I usecallback
, after the user grants the authorisation I'm shown a page with a verification token. What am I supposed to do with this token? Why the callback isn't called?The text was updated successfully, but these errors were encountered: