SAP Knowledge Base Article - Preview

3271841 - Configuring the Mail Adapter with OAuth2.0 the error "Access Refresh token can not be retrieved" is thrown

Symptom

You are Configuring the OAuth2.0 authentication to use to connect to the Microsoft mail server.

When calling the URL manually to generate the token, You get the error saying:

"Access Refresh token can not be retrieved. Please collect and cheek XPI Traces for further information".


In the XPI inspector traces example 100 you can found the bellow response instead of the token:

Response-Code : {"error":"invalid_client","error_description":"xxxxxxxxx: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'xxxxxxxxx'.\r\nTrace ID: xxxxxxxxxxx\r\nCorrelation ID:xxxxxxxxx\r\nTimestamp: 2022-09-13 14:12:51Z","error_codes":[7000215],"timestamp":"2022-09-13 14:12:51Z","trace_id":"xxxxxxxxxx","correlation_id":"Xxxxxxxx","error_uri":"https://login.microsoftonline.com/error?code=7000215"}



Read more...

Environment

SAP NetWeaver 7.5 SP17 or Higher

Keywords

Access Refresh token can not be retrieved, OAuth2.0, invalid_client, Mail Adapter , KBA , BC-XI-CON-MAI , Mail Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.