onepiecejs/nodejs-cantas

Google Authentication redirects back to login page, cannot log in

sgallagher opened this issue · 12 comments

sgallagher commented

I set up a Cantas instance on OpenShift (http://cantas-fedoraserver.rhcloud.com). I enabled Google Authentication (and set up a Client ID for it). When I click "Log in with Google", I am directed to the Google login, then prompted to allow Cantas to see my email address and basic profile information, and when I click "Approve", I'm simply redirected back to the login page again. This is preventing us from deploying Cantas.

xiaods commented

@sgallagher Got it, I will fix it this week.

xiaods commented

by the way, please check cat settings.json

...
"auth": {
        "strategy": "remote_user",
        "google": {
          "clientID": "xxx-xxxx.apps.googleusercontent.com",
          "clientSecret": "xxx",
          "callbackURL": "http://cantas-onepiecejs.rhcloud.com/oauth2callback"
        }
    },
...
sgallagher commented 
"auth": {
    "strategy": "remote_user",
    "google": {
        "clientID": "xxx.apps.googleusercontent.com",
        "clientSecret": "xxx",
        "callbackURL": "http://cantas-fedoraserver.rhcloud.com/oauth2callback"
    }
},

I assume that callbackURL is supposed to be pointing at my site, not yours?

xiaods commented

@sgallagher could you please re-check google console settings:

my app address is here:
https://console.developers.google.com/project/nodejs-cantas/apiui/credential
I think you also have same url to settings.

please check the cantas-fedoraserver app have correct settings:
screen shot 2014-12-15 at 11 40 14 pm

xiaods commented

i can't give you final solution, but i also found some weird thing, when i directly view http://cantas-onepiecejs.rhcloud.com/oauth2callback, i got 400 error, if you use your http://cantas-fedoraserver.rhcloud.com/oauth2callback, i will redirect to http://cantas-fedoraserver.rhcloud.com/login, i am not found the reason, i will check it asap.

sgallagher commented

OK, so that indicates that there's probably a setting I missed somewhere that defines that location.

sgallagher commented

What am I looking for? See #69 (comment) for what I have there...

xiaods commented

feel need patch to update README, the openshift settings maybe overwrite the settings again.

sgallagher commented

I set those values in init_settings which then pushed them to settings.json. Both are in agreement about the Client ID, Client Secret and callbackURL values

xiaods commented

@sgallagher when testing pass, i will merge the patch, it will keep cantas successfully deploy to openshift.