Credential verification failed with long token text

  • Resolved ratamatcat

    (@ratamatcat)


    6 months, 3 weeks ago

    Following your documentation to configure my first connection with FluentSMPT for Microsoft 365.

    As the Application Client ID field in FluentSMPT already contained a value I left that in place, and added the Client Secret Value from Microsoft Azure for the Application Client Secret field of FluentSMPT.

    However after clicking “Authenticate with Office365 & Get Access Token” button, Microsoft wasn’t able to sign me in, with the message:

    Request Id: 0aad8ca4-bc82-46a4-88c6-0670ff432200
    Correlation Id: 5ff3b8cb-d7e7-4292-9ae8-a7ebca9ee450
    Timestamp: 2024-05-07T04:07:21Z
    Message: AADSTS700016: Application with identifier ‘R’ was not found in the directory ‘(My Organization Name)’. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

    So I tried instead the Application (client) ID from Microsoft Azure and paste into the Application Client ID field in FluentSMPT. This additional step was not part of your documentation but seemed to work and I arrived at the Token Generation Page.

    Then I copied the generated token and provided it to the “Access Token” field of FluentSMPT and clicked Save Connection Settings but received the message:

    Credential Verification Failed. Please check your inputs

    Note that the token was very long, in contrast to the token in your documentation, it has 913 characters as opposed to 45 characters.

    Not too sure how to move forward at this point, and any advice is appreciated.

    Can I paste up my token here, would that help?

    Thanks,

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter ratamatcat

    (@ratamatcat)

    Since I posted this I have changed to Google Workspace so kindly ignore the above question.

    With Google Workspace setup I also encountered problems where at the oAuth consent screen there was a random error that stopped me from saving that section and moving forward. One of the fields had an incorrect entry but it didn’t say which one.

    Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @ratamatcat,

    Thank you for reaching out regarding your issues with FluentSMTP. I understand you’re encountering problems with credential verification.

    Regarding the excessive token length, it’s normal for Microsoft connections to have long tokens. Both long and short tokens are acceptable. We noticed sometimes users copy the Client Secret ID instead of the Client Secret Value and thus Credentials Failed.

    As you’ve mentioned, you’re now working with Google Workspace. For the OAuth consent screen, it’s crucial to check the following:

    • Web Application Type
    • Redirect URI

    Once these settings are configured, make sure to publish your App from the OAuth Consent Screen.

    If you’re still having difficulties, please feel free to share screenshots, and I’ll be glad to assist you further.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Credential verification failed with long token text’ is closed to new replies.