How To Fix /OSP/MSG479 - RFC destination &1 should select No Logon and Send SAP LogonTicket

SAP Error Message - Details

• Message type: E = Error

• Message class: /OSP/MSG -

• Message number: 479

• Message text: RFC destination &1 should select No Logon and Send SAP LogonTicket

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 /OSP/MSG479 - RFC destination &1 should select No Logon and Send SAP LogonTicket ?

  The SAP error message /OSP/MSG479 RFC destination &1 should select No Logon and Send SAP LogonTicket typically occurs in the context of configuring RFC (Remote Function Call) destinations in SAP systems, particularly when dealing with Single Sign-On (SSO) scenarios using SAP Logon Tickets.
  Cause:
  This error indicates that the RFC destination specified (denoted by &1) is configured to require a logon, but it should be set to "No Logon" and configured to send a SAP Logon Ticket instead. This is often encountered in environments where SSO is implemented, and the system is expected to authenticate users without prompting for credentials.
  Solution:
  To resolve this error, you need to adjust the configuration of the RFC destination in question. Here are the steps to do this:
  
  
  Access the RFC Destination Configuration:
  
  Go to transaction code SM59 in the SAP GUI.
  Locate the RFC destination that is causing the error.
  
  
  
  Edit the RFC Destination:
  
  Select the RFC destination and click on the "Change" button.
  In the configuration settings, look for the "Logon & Security" tab.
  
  
  
  Adjust Logon Settings:
  
  Set the "Logon Method" to "No Logon".
  Ensure that the option to "Send SAP Logon Ticket" is selected.
  
  
  
  Save the Changes:
  
  After making the necessary changes, save the configuration.
  
  
  
  Test the RFC Connection:
  
  Use the "Connection Test" feature in SM59 to verify that the RFC destination is now working correctly without prompting for a logon.
  
  
  
  Related Information:
  
  SAP Logon Tickets: These are used in SSO scenarios to allow users to authenticate without entering credentials multiple times. The ticket is generated by the SAP system and can be used to access other SAP systems seamlessly.
  RFC Destinations: These are configurations that define how one SAP system can communicate with another. They can be set up for various types of connections, including those that require user credentials or those that use SSO.
  SSO Configuration: Ensure that your SSO setup is correctly configured across all relevant systems, including the necessary trust relationships and ticket granting mechanisms.
  
  Additional Considerations:
  
  If you continue to experience issues after making these changes, check the system logs for any additional error messages that may provide further insight.
  Ensure that the user roles and authorizations are correctly set up to allow for SSO and that the necessary components (like the SAP Web Dispatcher or SAP Gateway) are properly configured to handle logon tickets.
  
  By following these steps, you should be able to resolve the error and ensure that your RFC destination is correctly configured for SSO using SAP Logon Tickets.