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

The OAuth callback validator was overly aggressive. Desktop applications... #33

Closed

Conversation

trevordevore
Copy link

... can use the localhost in order to listen for the response from the OAuth server. In addition, it may listen on a non-standard port. This updated code only verifies the scheme and host. It also adds a WP filter that allows localhost in the URL.

…ons can use the localhost in order to listen for the response from the OAuth server. In addition, it may listen on a non-standard port. This updated code only verifies the scheme and host. It also adds a WP filter that allows localhost in the URL.
sblaz added a commit to sblaz/OAuth1 that referenced this pull request Jun 2, 2015
sblaz added a commit to sblaz/OAuth1 that referenced this pull request Jun 5, 2015
@coderkevin
Copy link

(Looks like this has been out there for a while, but I'll comment anyway since it's still open and relevant)

This issue can be solved outside of the OAuth plugin by using an external plugin that adds the same filter. I wonder if that would make more sense because it could be configured differently per server.

@rmccue
Copy link
Member

rmccue commented Dec 7, 2015

This has been fixed in #98; thanks for the PR anyway! 🍰

@rmccue rmccue closed this Dec 7, 2015
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

Successfully merging this pull request may close these issues.

3 participants