How To Fix SAML2064 - Logon policy &1 was not found in client &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SAML2 - SAML2 Nachrichten

• Message number: 064

• Message text: Logon policy &1 was not found in client &2

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message SAML2064 - Logon policy &1 was not found in client &2 ?

  The SAP error message SAML2064 indicates that a specific logon policy defined in the system is not found for the specified client. This error typically occurs in the context of Single Sign-On (SSO) configurations using SAML (Security Assertion Markup Language).
  Cause:
  
  Missing Logon Policy: The logon policy referenced in the error message does not exist in the specified client. This could be due to a misconfiguration or an oversight during the setup of SSO.
  Client-Specific Configuration: The logon policy may not have been created or activated for the specific client you are trying to access.
  Transport Issues: If the logon policy was recently transported from another system, it may not have been properly imported or activated in the target client.
  
  Solution:
  
  
  Check Logon Policies:
  
  Go to transaction SAML2 in the SAP GUI.
  Navigate to the Logon Policies section and verify if the logon policy mentioned in the error message exists for the specified client.
  If it does not exist, you may need to create it or transport it from another system where it is defined.
  
  
  
  Create or Modify Logon Policy:
  
  If the logon policy is missing, you can create a new logon policy by following the steps in the SAML2 configuration.
  Ensure that the logon policy is correctly configured with the necessary settings for SSO.
  
  
  
  Transport Logon Policy:
  
  If the logon policy exists in another client or system, ensure that it is properly transported to the client where the error is occurring.
  After transporting, make sure to activate the logon policy in the target client.
  
  
  
  Check Client Settings:
  
  Ensure that the client settings are correct and that the client is configured to use the appropriate logon policies.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or guides related to SAML and SSO configurations for detailed steps on setting up logon policies.
  
  
  
  Related Information:
  
  SAML Configuration: Understanding how SAML works in SAP environments is crucial. Familiarize yourself with the SAML2 transaction and its components.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.