Question about Open ID being shut down
RyanTG opened this issue · comments
Next month, Google is shutting down Open ID. If I'm currently using my google profile to log into Enki, does that mean I won't be able to log in anymore? If so, any suggestions?
ref: https://developers.google.com/accounts/docs/OpenID#shutdown-timetable
Looks like they're still supporting OpenID connect. I haven't looked to see how different that is and whether enki needs updates to work with it.
Yeah, I wonder. I can't figure it out. Let me know if you probably won't have time to research/update it. In that case, I'll check into other blogging apps.
I just want to note that I think Enki is great! Except the whole third party login thing is a hassle, and this is a case in point (also, akismet support on comments would be nice).
probably not. Enki has dated a bit - externalizing comments and fixing up login would both be decent fixes. (Or honestly, using static site + external comments...)
I too still think Enki is great. But more as a reflection of my own laziness than anything else, I have been considering moving to something like Jekyll for a while now.
None the less though, I will always have a soft spot in my heart for Enki and should there be enough interest, I’d be willing to have a go at least at trying to fix up or swap out the OpenID stuff. I always thought it was great that Enki had a little more than the standard user/pass for admin login but I must admit I never found the OpenID stuff that easy to work with. Things having moved on a little since Enki really saw any development activity, I wonder if there may be some way to introduce some form of 2 factor auth or something…
On 22 Mar 2015, at 12:32 pm, Xavier Shay notifications@github.com wrote:
probably not. Enki has dated a bit - externalizing comments and fixing up login would both be decent fixes. (Or honestly, using static site + external comments...)
—
Reply to this email directly or view it on GitHub #97 (comment).
I added disqus on my enki site, and it works well. But I've since grown to dislike the idea of a third party advertising company hosting my site's comments.
And for totally different reasons, I'm not into static sites. I like having the option of posting from wherever I am (work, phone, home, the lab at school, etc). Plus I edit the heck out of each post, and repeatedly deploying seems like a hassle. As far as I know, that isn't really possible with Jerkyll and the like. Enki is appealing because it doesn't contain loads of features that I'll never use. It does everything I want it to. I may switch to Publify, since it seems to have a nice admin and post editor. Still researching.
Those are all good points.
@xaviershay what are your thoughts on auth for Enki? I’m thinking I could look into updating to the OpenID support, or perhaps go a totally different way and look at a new auth mechanism that makes use of the Google Authenticator API or something similar. I really haven’t looked very far into this option, so I’m not even sure if it’s viable for an open source project. And is this too elitist an assumption that the Enki user base would all have a device that supports something like Google Authenticator?
On 22 Mar 2015, at 5:33 pm, RyanTG notifications@github.com wrote:
I added disqus on my enki site, and it works well. But I've since grown to dislike the idea of a third party advertising company hosting my site's comments.
And for totally different reasons, I'm not into static sites. I like having the option of posting from wherever I am (work, phone, home, the lab at school, etc). Plus I edit the heck out of each post, and repeatedly deploying seems like a hassle. As far as I know, that isn't really possible with Jerkyll and the like. Enki is appealing because it doesn't contain loads of features that I'll never use. It does everything I want it to. I may switch to Publify, since it seems to have a nice admin and post editor. Still researching.
—
Reply to this email directly or view it on GitHub #97 (comment).
Probably the best option would be to port it to omniauth, making it easy to set up your own authentication - it already supports openid connect by the looks of it https://github.com/jjbohn/omniauth-openid-connect
OK, will look into it when I get a little time.
On 23 Mar 2015, at 3:18 am, Xavier Shay notifications@github.com wrote:
Probably the best option would be to port it to omniauth, making it easy to set up your own authentication - it already supports openid connect by the looks of it https://github.com/jjbohn/omniauth-openid-connect
—
Reply to this email directly or view it on GitHub.
@RyanTG check out the updated README for instructions on how to use Google OpenID Connect with Enki.
Hmm, the Travis build seems to be failing, I thought I fixed up all the tests, but perhaps not. If anyone has some time to sort this out, that would be great. Otherwise I'll look into it at some point soon when I get some more time.