“Inactive Oauth”

  • Resolved mmcevoy

    (@mmcevoy)


    5 years ago

    This isn’t a query about a page, but about an email received from “Google Developers” stating that the OAuth URI for postman will be removed for non-compliance with URI Validation rules?

    I’m not clear on how I’m receiving this as a “developer”, since I just use Postman SMTP…

    Email states:
    “`We are writing to let you know that you have inactive OAuth redirect URIs and JavaScript origins in your Google Cloud project that are not in compliance with Google’s OAuth URI validation rules.

    On July 12, 2021, we will remove all inactive URIs that are invalid.
    On September 13, 2021, we will remove all URIs that are not in compliance with redirect URIs and Javascript origins rules (including formerly inactive URIs trying to become active).

    What do I need to do to be compliant?

    If these inactive OAuth redirect URIs and JavaScript origins are no longer needed, you can remove them from your Google Cloud project. If they remain inactive, they will be automatically deleted after July 12, 2021.
    If your app still needs to use these URIs, please update your app and OAuth configuration from the Google Developer Console to use redirect URIs or JavaScript origins that are compliant with the OAuth URI validation rules by September 13, 2021.`”

    (I’m not clear if I can post the rest in an open forum because it contains URLs to our site admin side, and some client ID stuff..) Say

    In any case, if this is just me.. .WTH? If not, how do we solve this? Do I need to find a different SMTP solution for WordPress?

    I should add: there are no issues with using PostSMTP at this time. It works perfectly well on our site.

    Thanks for any guidance you can provide.

    • This topic was modified 5 years ago by mmcevoy.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • squill1959

    (@squill1959)

    5 years ago

    It is not just you, I have received the same emails. I too am interested to know what to do now.

    Tim

    (@tneville)

    5 years ago

    Hi @mmcevoy and @squill1959,

    Please could you let me know if you are using (free, personal) Gmail or Google Workspace (for business)?

    Either way, you have a ‘project’ set up in the Google Developer console which is either inactive or misconfigured. If you are not using it, you should delete it. If you are, you should correct the configuration.

    Hope this helps.

    Kind Regards,
    Tim

    Thread Starter mmcevoy

    (@mmcevoy)

    5 years ago

    Hi Tim,

    Thanks for responding. Please Advise: you’re stating the “project” has no connection to Postman SMTP despite the fact it directly addresses Postman SMTP in the statement?

    I’m very confused by this statement. I believe the “project” was set up for OAUTH setup with PostSMTP. As such, it is active (very, in fact, because we get 10 to 30 messages/day through Post SMTP on our website).

    We are using just basic GMAIL smtp with OAUTH on our end.

    Now, as far as configuration… what would be incorrect it in as long as it’s working perfectly fine? There’s nothing advising what the issue is, so I wouldn’t know what to “correct” with the configuration as there’s no logging advising of an issue.

    Thanks for your time today.

    Tim

    (@tneville)

    5 years ago

    Hi @mmcevoy,

    Please could you create your own thread and link back to this – it will be easier to dig into a bit more detail with your case specifically on your own thread. I don’t want to hijack this thread.

    Kind Regards,
    Tim

    Thread Starter mmcevoy

    (@mmcevoy)

    5 years ago

    Uh… very very confused now. I’m answering in the support query that *I* created, so please advise… what? I mean, I’m in the thread i created, so… You’re just confusing me more here, Tim.

    Thanks.

    Tim

    (@tneville)

    5 years ago

    Ignore my last comment, it’s very late and I’m more tired than I realised! I will get back to you shortly.

    Kind Regards,
    Tim

    psuds

    (@psuds)

    4 years, 12 months ago

    Following up – I got the same message from Google. I’m pretty sure the issue is this:

    URIs *
    Invalid Redirect: This app has a publishing status of “In production”. URI must use https:// as the scheme.

    The key is the https:// as the scheme. My URI is pointing to a http:// as the redirect.

    Can anyone confirm this is the same for them?

    Tim

    (@tneville)

    4 years, 12 months ago

    Hi @mmcevoy

    Are you using the Gmail API, or SMTP? I would assume the API based on your previous comments. The below article will help you cross check your settings.
    https://www.cloudways.com/blog/post-smtp-mailer-fork-of-wordpress-postman-smtp-plugin/?id=339490

    @psuds – I have seen this before. It is not uncommon for a HTTP/HTTPS mix up to cause a problem like this. Have you managed to get it working?

    Kind Regards,
    Tim

    Thread Starter mmcevoy

    (@mmcevoy)

    4 years, 11 months ago

    Following up. I believe I’ve figured out the issue:
    So, in the console, we put both the primary (northvillelibrary.org) and a secondary (www.northvillelibrary.org) as referring URIs.

    On the website, it uses the primary exclusively. So the complaint was about “non-use” of the http://www.northvillelibrary.org URI, which… wasn’t being used.

    So, worth consideration for this complaint would be: if you have sub/extra domains assigned to the “app” on the console side, make sure they’re being used.

    Thanks for the guidance to get us there, Tim!

    Tim

    (@tneville)

    4 years, 11 months ago

    Hi @mmcevoy,

    Thank you so much for following up, that’s really interesting information!

    Kind Regards,
    Tim

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

The topic ‘“Inactive Oauth”’ is closed to new replies.