Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SAML2 - SAML2 Nachrichten
Message number: 142
Message text: Only persistent name ID format is supported on register endpoint
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SAML2142
- Only persistent name ID format is supported on register endpoint ?The SAP error message SAML2142: Only persistent name ID format is supported on register endpoint typically occurs in the context of Single Sign-On (SSO) configurations using SAML (Security Assertion Markup Language). This error indicates that the SAML assertion being sent to the register endpoint is using a NameID format that is not supported by the endpoint.
Cause:
The error is caused by the use of a NameID format that is not "persistent." In SAML, the NameID is a unique identifier for a user, and there are different formats available, such as:
The register endpoint in your SAP system is configured to accept only the "persistent" NameID format. If the SAML assertion being sent uses a different format (like transient or email), the system will reject it and throw the SAML2142 error.
To resolve this error, you need to ensure that the SAML assertion being sent to the register endpoint uses the "persistent" NameID format. Here are the steps you can take:
Check Identity Provider (IdP) Configuration:
Update Service Provider (SP) Configuration:
Testing:
Consult Documentation:
Contact Support:
By ensuring that the correct NameID format is used, you should be able to resolve the SAML2142 error and successfully authenticate users through the register endpoint.
Get instant SAP help. Sign up for our Free Essentials Plan.
SAML2141
Can't store consumed artifact in DB. Subrc: '&1'
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SAML2140
Method '&1' from BAdI implementation has thrown an exception: '&2'
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SAML2143
Automatic account creation - response is expected on register endpoint
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SAML2144
Unknown trusted entity type: '&1'
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.