GreenLight - Google error

[James O. Stanworth]

When implementing the GreenLight BBB front end I get the following error from Google:

Error: invalid_client

The OAuth client was not found.

Request Details

• access_type=online
• client_id=519[all but first and last 3 deleted by me]be2.apps.googleusercontent.com
• redirect_uri=http://stanworth.org/b/auth/google/callback
• response_type=code
• scope=profile email
• state=0ac31c0b5a0de2df1745d5a5185bf8b414ea55a0238c295c

That’s all we know.

The relevant lines in the env file are:

GOOGLE_OAUTH2_ID=519[ deleted as above ]be2.apps.googleusercontent.com
GOOGLE_OAUTH2_SECRET=XaT[ deleted as above ]6B_
GOOGLE_OAUTH2_HD=

I have restarted the server (i.e., stop, remove and re-run docker).

For Google:

APIs are enabled

Credentials are as follows

Client ID 519[ as above ]be2.apps.googleusercontent.com

Client secret [XaT[ as above ]6B_

Creation date Oct 12, 2017, 8:01:11 PM
Name stanworth_bbb
Restrictions

- nothing input for Authorized JavaScript...
Authorized redirects
https://stanworth.org/b/auth/google/callback [Note - documentation is http - but the server is now secured so https?]

The dashboard does not show any activity.

I do not know why Google return as error with http not https. Does Google take time to update? My original link was http and I corrected that.

Is the e-mail state of any relevance here?

Thanks for any help

[Joshua Arts]

Have you filled out the consent screen in the Google Developer Console?

Under the "API and Services" sidebar, select "credentials". Then select the "Oauth consent screen" tab and fill out the form. You should only need product name and email.

If you've already done this, then this is odd. Perhaps try recreating your credentials (and your Docker container when you change the env file).

[James O. Stanworth]

Thanks. I had filled up the consent screen and enabled the API. I also ammended the product name to avoid any special characters or spaces (though not the issue)
Also I recreated new credentials, copied to the env and remade the container.

Here is Google's error:
Request Details

• access_type=online
• client_id=519[ ... ]a93.apps.googleusercontent.com

• redirect_uri=http://stanworth.org/b/auth/google/callback
• response_type=code
• scope=profile email

• state=1c2fb20ce27d9f3d726d2be9dbee573c2a2a7001a

I do not follow why the redirect is still http? Is this getting stuck in a cache somewhere?

Is the 'state' some kind of diagnostic?

When I click on the greenlight front page for the login I get taken to the server page:

http://stanworth.org/b/users/login

but things break after that.

Could I have some kind of permission problem?

Or is this the Google's issue? (Kind of ironic the rest of BBB works but the Google bit dies - considering the scale of both)

[James O. Stanworth]

After restarting the server, updating (minor) and remaking the greenlight container it worked partly. I could enter the BBB environment and while the microphone worked the buttons would not.

I exited and then tried again only to get this message from Google:

400. That’s an error.

Error: redirect_uri_mismatch

The redirect URI in the request, http://stanworth.org/b/auth/google/callback, does not match the ones authorized for the OAuth client. Visit https://console.developers.google.com/apis/credentials/oauthclient/519189883467-hrkvqlr89ud4f9kuj4294rrsitq0sa93.apps.googleusercontent.com?project=519189883467 to update the authorized redirect URIs

When pasting the Google keys / ID in to the env file there was a space after the key. I don't know if that mattered but all spaces are removed.

If it is the redirect problem could it be the format of that line in Google setup (redirect).

There is debate online as to whether to add www.

There is no forward slash at the end of the redirect is that needed?

My server setup runs BBB both http and https (as per instructions as passes the security test BBB suggests with the A grading).

Could you suggest any tests to run to try and get some sense of where the problems lies? Joshua your suggestion before helped solve my key problem -- anything similar to solve this issue?

Frustrating! My irritation with Google grows... The install of BBB has been pretty smooth until Google walked in the room.

[Joshua Arts]

It looks like the URL it is trying to redirect to as a callback URL is not authorized. If you are running your server on https, you need to authorize https://stanworth.org/b/auth/google/callback. It might be best to just authorize both the https and http protocols since you can authorize many callback URL's. 

[James O. Stanworth]

Sorry for the slow reply / incomplete wrap-up off this issue.

My colleague could login using Google while I couldn't. Once I added both the https and http protocol it worked (and I could login as well as my colleague!).
So it seems best to have both protocols to ensure the login works.

Joshua - thanks for the quick follow up