Re: HybridAuth in favour of our own OpenID implementation.
Reply #1 –
I like the idea of a library for that ... its one of those specialized areas, that yes we can do but then there is the ongoing maintenance care and feeding ... seems like our time is better spent elsewhere.
Personally I'd like that in 1.0 ... the ability to use your google login etc is very nice, plus some of the capabilities of that lib will work nice in the profile area (something for 1.1 is a revamp of that). Just having it in place gives addon writers something cool to play with as well.
Looks "easy" to plug in, not sure how much work is involved to integrate it.
Re: HybridAuth in favour of our own OpenID implementation.
Reply #4 –
Looking forward to how it integrates ... bummer there are bugs right up front, with all the activity on that I'm kind of surprised.
Re: HybridAuth in favour of our own OpenID implementation.
Reply #9 –
Let's say that playing with it few minutes I did:
1) extend the class to rewrite the parseUri method in order to handle Elk's url schema instead of "friendly urls",
2) played a bit with github and google,
3) failed firstly because of localhost settings, then fail because of a redirect loop...
It seems kind of working, but there is some trick I'm missing... lol