An OpenID integration into the new release will be excellent
A MODx Fanatic
-
MODX Staff
- 12,272 Posts
Plans since 2006 have changed. There is no OpenID currently on the roadmap, though third-parties are certainly welcome to implement a plugin to auth in that manner.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
thanks for this info! I admit I didn’t even notice the age of what I quoted.
Even if it’s an old thread, I think it deserves some bumping
I hope someone jumps in and write an OpenID plugin, this would open doors and facilitate integration with 3rd party applications (some forums support OpenID for instance)
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
OpenID is a great initiative, one with traction over a wide variety of contemporary web services, and it would be a great addition to revo and/or evo.
I’ve created a package for Revo that logs webusers in using Open Id. It’s basically a clone of the Login component but rather than user/password you have user/openid url. The heavy lifting for the protocol is done by the JanRain libraries,other than that it just consist of a snippet, two chunks and a plugin. Transport package and zipped build area attached.
So, a user enters his MODx user name and his open id URL, presses login, this starts the server auth protocol with the open id auth provider, it may redirect to the site auth where the user then enters his password(open id, not MODx) and presses continue. It then redirects back to the same page you are on in MODx where the auth response is checked. If OK the login processor is executed, this eventually fires the ’OnWebAuthentication’ event which the plugin captures. This does a sanity check that we are a correct openid auth then returns ’true’ to the login processor. This then accepts that 3rd party authentication has taken place, doesn’t do the password check, carries on with the login and Voila! the user is logged into MODx as a web user. Error messages fed back as appropriate.
Ok, I’ve not put this in extra’s yet as I’m not sure where to go next, with it. We could :-
1. Spruce up(add lexicon etc.) and ship it into extra’s. This will give us two login components for users to chose from, they can use one or the other or both.
2. Do 1 above but add a password box, so the component can be used for normal login and open id login. This again gives us two login components, this one now overlapping functionality with the Login component. Maybe add config params to the snippet which say method is needed.
3. Rip the front end off and merge the back end into the existing Login component, making it like option 2 above but we now have only one component that’s controlled and managed as a modx-component, not an extra. This will take more time than 1 or 2 above.
Any thoughts? I would lean to option 3 but I’m happy to do whatever everybody wants.
Use MODx, or the cat gets it!
