Google “Error 400: invalid_request” when trying to authenticate

  • Resolved Brian Shim

    (@brianrshim)


    3 years, 11 months ago

    When I try to authenticate with Google, I get this error:

    Authorization Error
    Error 400: invalid_request

    You can’t sign in to this app because it doesn’t comply with Google’s OAuth 2.0 policy for keeping apps secure.

    You can let the app developer know that this app doesn’t comply with one or more Google validation rules.
    Request Details
    The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.
    If you’re the app developer, make sure that these request details comply with Google policies.
    redirect_uri: urn:ietf:wg:oauth:2.0:oob

    Could it be related to this OOB deprecation?
    https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html

    Thanks,
    Brian

Viewing 2 replies - 1 through 2 (of 2 total)
  • ocsaroy

    (@ocsaroy)

    3 years, 11 months ago

    Any news on how to get FluentSMTP worked with gmail ?
    I have the same Error 400: invalid_request

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    3 years, 11 months ago

    Hi,

    Sorry, we missed your ticket earlier. For any further queries, please open a support ticket in our dedicated support channel for a faster response.

    As Google has updated the API settings the error is coming. According to our investigation, it appears that if you are a Google WorkSpace user then you need to set the user type to internal.

    Furthermore, if you are a free Google user, you must connect to the app in test mode as an external user. After connecting the app, you must publish it from testing so that your API key does not expire.

    We will update our documentation soon.

    Thank you

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Google “Error 400: invalid_request” when trying to authenticate’ is closed to new replies.