Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author hectavex

    (@hectavex)

    You are very observant ?? Happy New Year.

    To answer your question, it’s not finished and you shouldn’t try to enable it.

    I was actually building the Battle.net provider file a while ago, but I think they require your redirect URL to be HTTPS which I don’t currently have on any of my WP sites, so I couldn’t finish it up. Maybe I can setup a localhost site with free HTTPS cert + dynamic dns and develop/test it that way.

    We do currently check the HTTPS cert during the handshakes as recommended by Battle.net, but I don’t have an actual site secured with HTTPS which they also require. Not all providers are like this, but I applaud them for taking extra security steps.

    https://dev.battle.net/docs/read/oauth

    I am going to mark this as resolved, but you can expect to see Battle.net eventually, and if you want to discuss further please feel free to do so at the Github repo.

    https://github.com/perrybutler/WP-OAuth

    I would like to see this working as well…

    I do have a https secured site, is there some way you could walk me through getting this setup on the settings page so I can “test” this for you?

    Thanks!

    Managed to get it “working” but I get this error.

    error=”invalid_grant”, error_description=”Invalid redirect: https://maxthreat.us/ does not match one of the registered values: [https://dev.battle.net/, https://maxthreat.us/wp%5D”

    I’m not sure where it’s getting the invalid site yet, but I’ll track it down but if you can provided some insight that’d be awesome…

    Plugin Author hectavex

    (@hectavex)

    I think this issue has been fixed in the latest commit, but it hasn’t been rolled out as a plugin update yet. We were using SERVER_NAME when we should have been using site_url, so it’s probably auto-populating the HTTP calls with an incorrect redirect url. I’m hoping to roll out an update later today, I synced the repo earlier and just need to test it across a few sites first.

    You could refer to the latest commits at the Github repo here, which should contain the fix that will be rolled out soon.

    Looks like that is working, but users are being called “userX” when they sign up for the site. Is there a way to use a battle tag or allow them to select one of their character names?

    Thanks!

    Plugin Author hectavex

    (@hectavex)

    Not at the moment. Those features are unique to Battle.NET and this plugin doesn’t incorporate any unique provider features at the moment. It treats every provider the same, using methods that are universal to all providers and non-invasive to user privacy.

    The usernames are similar to and inspired by Stackoverflow’s model.

    Your ideas are logical, so I would suggest opening an issue (feature request) at the Github repo so others who might want to contribute may track it and perhaps implement it before I get a chance to.

    With that said, use the Battle.NET provider at your own discretion/risk and remember it’s not an official provider in WP-OAuth yet.

    I’ll poke around on it at this point and see what I can come up with. Thanks for getting me this far.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Battle.net’ is closed to new replies.