SAP Knowledge Base Article - Preview

3602026 - OAUTH Session is already personalized (cannot logon twice)

Symptom

When trying to authenticate with OAUTH 2.0 access token, request fails with a 401 Unauthorized status, and work process trace (SM50) contains the following error:

OAUTH2: Error! CX_OAUTH2_EXCEPTION thrown, time: <date> <hour>
N  OAUTH2: Error Text: Authentication failed.
N  OAUTH2: HTTP Status Code: 401
N  OAUTH2: error_description: Authentication failed.
N  OAUTH2: error: authentication_failed
[...]
N  *** ERROR => OAuthLogon: session is already personalized! [sign.c       14236]
[...]
N  OAUTH2: Prev. Ex. Text: Session is already personalized (cannot logon twice)


Read more...

Environment

  • SAP S/4HANA
  • ABAP Platform

Product

ABAP platform all versions ; SAP S/4HANA all versions

Keywords

OAUTH, OAuth 2.0, SAML beater, OAuthLogon, Session is already personalized, cannot logon twice, authentication_failed, Authentication failed , KBA , BC-SEC-LGN-OA2 , OAuth 2.0 for ABAP , 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.