ah0265

Wow – what a comprehensive (and quick!) response!

Lots to digest and play with… I’m sure I will be back with more questions later but for now thank you very much!

Hmmmmm… it recovered on its own… I got an initial fatal error message followed by a ‘Sorry, the site is temporally unavailable’ for about 5 minutes, then it just came back up. Hooray!

My 4.2 upgrade seemed to go OK, but it cratered when I updated the plugins. Hope my backup is good!

I have good news for those of you following this thread… I have created a functioning plugin that allows you to authenticate your WordPress users on the Neon platform.

I did this by shamelessly hacking Cliff Griffin’s simple-ldap-login plugin, ripping out the LDAP stuff and inserting what was required to make it work with Neon.

It is working well for me… it drops in on top of the native WordPress login process and uses API calls to the Neon server to validate the UserID and Password supplied by the user.

I am willing to share my version (simple-neon-login) with anybody who is interested.

z2systems has just (March 2015) released preliminary information on a new OAuth tool… here is how they describe it:

NeonCRM can act as an OAuth 2.0 provider. This means that NeonCRM’s existing login system can be used to authenticate access to a third-part website or service as a single sign-on.

Full details are available at this URL:

https://help.neoncrm.com/api/oauth

OK, but s2Members appears to be keeping information about each user someplace other than the users table. I have found s2Members methods for reading this information: are there methods that will allow me to write/update information about a user? (This would allow me to create an entry for a new user in the users table and then let s2Members know what access level they should have).

I agree… you would think in would be in Z2’s best interest.

I contacted their support center asking what they did have to offer and got this reply: maybe the links will be useful to you.

We don’t have much in the way of WordPress-specific examples, though we have release some tools that may be new to you. The only thing we have that ties the API to WordPress right now is an events widget (https://www.ads-software.com/plugins/neoncrm-events-widget/) which may be useful as a reference point, if only for the basic API connection elements. I suspect you might get some mileage out of our PHP client library, which makes working with our API much simpler to manage. You can find that here: https://github.com/z2systems/neon-php.

Additionally, we do plan to release OAuth 2.0 capabilities in the next few months that will allow NeonCRM to act as a primary authenticator for a third-party system such as WordPress. We don’t have much information available yet, but keep an eye on our API roadmap page for updates (or consider signing up for email updates): https://help.neoncrm.com/roadmap

I am starting serious work on my port to WP… I will post again if I learn anything that may be helpful.