Authorization Error 400: invalid_scope

2,183 views
Skip to first unread message

Mike McLoughlin

unread,
Jul 31, 2022, 9:32:29 PM7/31/22
to GAM for Google Workspace
Hi

(Version: 6.064)

I began seeing the 'No client access allowed' error - as seen in this thread:

However, the gam oauth create flow (with default scopes selected) takes me to this Authorisation Error 400: invalid_scope page - see screenshot:
Screenshot 2022-08-01 02.20.59.png

This has been done many times previously without a problem and a "normal" GAM installation is still working fine.

Please advise.

Thanks

- Mike


Jay Lee

unread,
Jul 31, 2022, 9:34:36 PM7/31/22
to google-ap...@googlegroups.com
Your screenshot clipped the most important lines at the bottom (invalid scopes)

Can you share w fresh screenshot?

Jay

--
You received this message because you are subscribed to the Google Groups "GAM for Google Workspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/d9cc795b-e82d-46cf-ad5e-48fe4799738an%40googlegroups.com.
Message has been deleted

Mike McLoughlin

unread,
Aug 1, 2022, 1:07:13 AM8/1/22
to GAM for Google Workspace
Hi again, Jay

The error page was truncated and so needed a little dev tools adjustment to be able to see the full test. Here is now the requested screenshot:

Screenshot 2022-08-01 06.05.31.png

- Mike

On Monday, 1 August 2022 at 02:47:07 UTC+1 Mike McLoughlin wrote:
Hi Jay

Apologies, it is 3am here so my sight is a little fuzzy so I didn't notice that bottom one, lol.

This is the only invalid scope mentioned:



- Mike
____________

Mike McLoughlin

unread,
Aug 1, 2022, 11:42:12 AM8/1/22
to GAM for Google Workspace
Ok, after a video chat with Ross, the cause and workaround can be shared.

Basically, the cause is the oauth URL is too long for the browser to take from the command line but ok to be copied from the terminal window and pasted into the browser directly.

That then worked for me.

- Mike

Reply all
Reply to author
Forward
0 new messages