hectavex

Rich, you could remove the plugin folder via FTP. If you’re unsure how to do that let me know.

My apologies for the rough time and delay on my reply – I think I’m finally subscribed to emails for this forum. ??

I haven’t tested if this plugin works on localhost since I normally develop and test it with a live devsite. I’ll try it out on localhost and let you know.

You could also try the new version v0.3; there is a redirect_url fix which may help.

Files get duplicated to SVN for a plugin update and not much else. The Github repo is where active development takes place.

hdeadman, thanks for the feedback!

I agree with your first point, we need a website with step by step instructions and screenshots for how to set up the various providers.

As for your second point, it’s a good request. I’m adding it to the Github repo here as an issue to be tracked and implemented.

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 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.

Hi Thakksy,

I’m not sure why I stopped getting notifications from this forum, sorry for the delayed response. Compatibility with those plugins is on the roadmap, but it hasn’t been tested with either of them at all yet. Your mileage may greatly vary. ??

I’m going to close this, but if you have any suggestions for how you’d like to see this work alongside BuddyPress or bbpress let me know at this forum or at the Github repository. Thank you.

Hi Runn.Vermel,

I’m not sure why I stopped getting notifications from this forum, sorry for the delayed response. You can only authenticate with the services that you’ve configured in the WP-OAuth Settings page, other services won’t work.

The current version should be capable of authenticating with Google, Facebook, LinkedIn, Github, reddit, Windows Live, PayPal and Instagram.

If you have recommendations for a service or feature feel free to let me know.

Hi piantadosi,

I’m not sure why I stopped getting notifications from this forum, sorry for the delayed response. If it happens every N minutes it might be the login timeout feature. I’m going to check this out on my end and get back to you.

Hello @theiggep,

This plugin is quite new so you won’t find much about it with a Google search. I appreciate you giving it a try out ??

I’m assuming you’ve already supplied the Client ID/Client Secret for Google on the WP-OAuth settings page, since the error you’re seeing happens at the last step of the authentication flow.

This could be difficult to troubleshoot without knowing more details such as your site URL, plugin settings and other plugins in use, which may expose sensitive or personal info about yourself. Because of that I am asking you contact me via email where I can assist you privately.

[email protected]

It would be nice if the plugin had a debug option which outputs the provider API payloads for us to inspect, but that would expose lots of info (security concern) and users might forget to turn it off.

If you’re feeling like a hacker today or would rather try to investigate yourself, you could do what I normally do to debug these issues by opening up the login-google.php file, find the line $oauth_identity = array(); and put this above it: echo print_r($result_obj); die;

That will let you visualize the final API payload on the page (which normally contains the authenticated user’s OAuth identity), and it will prevent WordPress from continuing to load, so make sure you remove that line when you’re done investigating.

I’ll leave this issue open until I hear from you and we find a solution.

Thanks,
Perry

In re-reading your question, my reply was hasty. I see that you want to be able to restrict access to a domain, thus limiting the group of people who can register/login.

That is a great idea for a feature. I’ve added it as an issue tagged ‘Enhancement’ at the Github repo here. Refer to that issue if you want to track development on this feature. I’m going to mark this resolved.

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

Thanks ??

Twitter hasn’t been added yet because they still use OAuth 1.0a. Not that 1.0a is bad, but it means the OAuth 2.0 code I’ve built doesn’t work for that, so I would need to code the 1.0a separately, or toss in a Twitter library, and I’m trying to avoid extra libraries at the moment. I’d like to add Twitter login, perhaps in the near future.

When you try out the plugin feel free to let me know how I can improve it!

Not yet possible, it is by design. This question is active at the GitHub repo here where we’ll track any further developments related to it. Thanks!

I wasn’t able to reproduce this issue. Since I haven’t heard back I’m going to mark this as resolved. If you still have this issue, feel free to open another topic or contact me by email. Have a good one!