arch7stanton

Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Forum: Plugins
    In reply to: [HTTP Digest Authentication] Discussion questions
    Thread Starter arch7stanton

    (@arch7stanton)

    9 years, 8 months ago

    Hi Jesin,

    Thanks for your comments, and for taking the time to find the link to HowToForge. I use this Apache capability already to protect phpMyAdmin and some other directories. I will give more thought to your suggestion.

    I had hoped to avoid duplicating the user management capability of WordPress (lost username, lost password, associate multiple email addresses with one account, etc). But given how difficult it has been to succeed with this architecture you might be right.

    Thanks and best regards,
    Russell

    Forum: Plugins
    In reply to: [WP OAuth Server (OAuth Authentication)] The request method must be POST when requesting an access token
    Thread Starter arch7stanton

    (@arch7stanton)

    10 years, 2 months ago

    My bad Justin. I am in fact sending a GET rather than a POST. I dug into the OAuth server-side logs and can see the ?oauth=token post hitting the server as a GET request. Nearest I can figure is that when my back end mod_perl-enable apache returns the POST request to the front-end (non-mod_perl) apache it is being converted to a GET before being sent to the OAuth server.

    I tried using curl from the command line and it returned the JSON payload having the access_token. yay! Now I’m trying to implement a perl WWW::Curl wrapper around curl.

    Thanks for your help!

    Forum: Plugins
    In reply to: [WP OAuth Server (OAuth Authentication)] The requested URL /oauth/authorize was not found on this server
    arch7stanton

    (@arch7stanton)

    10 years, 2 months ago

    Hi lunitic,

    I found your post whilst researching the same message. I notice 2 potential problems with URL you posted.

    1) in the URI you posted, it looks like there is a double slash (“//”) between the hostname and “oauth”. You’ve “192.168.101.217//oauth” in your URL. Although often double slashes like that get figured out, no sense adding to the confusion. Eliminate one of those slashes and check if that helps.
    2) the value of your redirect_uri argument is not encoded. I think (but honestly, I am not certain) that the value “http://192.168.101.139:3000/_oauth/wordpress” needs to be encoded for HTML entities. For example, it should look something like “https%3A%2F%2F192.168.101.139%03A3000%2F_oauth%2Fwordpress.

    Please check both of these issues and then post your results.

    Good luck!

Viewing 3 replies - 1 through 3 (of 3 total)