Unable to register new OpenID domains with Google

[justinhenricks]

I've gotten BarKeep up and running with localhost, however when I go to view it using my IP address, eg. 192.168.1.xxx I am getting this 400 error:

OpenID auth request contains an unregistered domain:

This makes me think that there is some exception for using localhost, but for any other domain (and if I push this to a server) it is not going to work with any other domain.

After doing some research it appears that as of May 19, you are unable to register new domains with Google. Has anyone else experienced this or have a work-around?

[sangameshm]

I just did a installation from scratch on ubuntu 12.04 LTS and i am facing the same issue. This ope id thing is turing aout to be Achilles heel to try out barkeep.

[chasseurmic]

Same here. Is it possible that the issue is related to the fact that the request is coming from an IP address instead of a named domain?

[jalvz]

Same here, also installed from scratch on Ubuntu. Is there any update on this?

[JuergenKindler]

Same problem :-( So GoogleID is dead, Yahoo OpenID does not work. Took one Java based, but that also does not work. Basically no way to log in :-( Stopping evaluation ... :-(

[gfodor]

same here. :( project seems effectively dead until someone upgrades it to support OAuth 2.

[amiraliakbari]

Same problem. Is there any way to login/create users without openID?

[mmmdamin]

same problem :(((((((((((((

[mhaamann]

Same problem here. Sadly i dont know ruby so i cannot create a fix. Anyone? Or is the project dead?

[cciotti]

Looks like it. Too bad. :-1:

[jpwdesigns]

Wish I had seen this thread before spending a couple hours setting it up.

[philc]

Guys, the project is not dead. We haven't gotten a chance to look at this because it works for us.

We'd be happy to merge in a pull request for another auth mechanism other than openID.

[dcaravana]

Same here. No pull requests yet? Any news? Thanks.

[amiraliakbari]

"OpenID 2.0 for Google accounts is going away." link Will this affect existing installations of Barkeep? Also I think this issue deserves paying more attention, as it really prevents new users from trying Barkeep.

[philc]

This hasn't been urgent for me because my Barkeep installations work fine, but it looks like this will affect existing installs soon. We'll need to get a fix/replacement. Proposals are welcome!

[jpodeszwik]

I implemented google oauth2 authentication here, but i don't guarantee it will work well (i.e. Sign out doesn't work yet): https://github.com/jpodeszwik/barkeep/tree/oauth2

You can test it by cloning my branch: git clone -b oauth2 https://github.com/jpodeszwik/barkeep.git

To test it you need to create project on google developers console: https://console.developers.google.com and add redirect uri to your app (it cannot be private ip afaik, but localhost works fine for testing): http://your_app_uri_with_port/signin/complete

In application config you should set OAUTH2_CLIENT_ID and OAUTH2_CLIENT_SECRET (example config in files environment.prod.*)

If you want, I can clean up my code and make pull request, but should I make backwards compatible changes (shold openid also work? Afaik it's going to die anyway)?

[fhanik]

There is a work around for this

Create a tunnel from your machine to the barkeep server, so that you can use localhost:8040

for example

ssh yourusername@yourbarkeepserver -L 8040:localhost:8040

then use http://localhost:8040/admin

and login with a google account. this will make the domain be localhost, and barkeep will create your user account

It's a short sighted solution, but managing users seems to be somewhat of a pickle here

[ygreif]

Having the same problem

[syntithenai]

https://github.com/jpodeszwik/barkeep/tree/oauth2 works for me

Would be valuable to git pull seeing as how default branch is broken now that google auth has changed.

[BenRomberg]

Another workaround that worked for us is to use https://openid.stackexchange.com/openid/provider for OPENID_PROVIDERS in environment.rb. That way, you can use it with arbitrary email addresses using StackExchange accounts.

[zdyn]

First off, apologies for the delay! We've implemented support for authentication using OAuth2 (Google only for now). There are updated instructions on the wiki, which you will need to follow if you plan on using OAuth2. I'm resolving this issue as I believe this addresses the primary concern.

Note that OpenID support was retained, so if you choose to use a different OpenID provider, feel free, but authentication via Google OAuth2 is what we recommend and will be the new default.