Logon and Security

On the Logon and Security tab page in transaction SM59, you can configure various logon data, authentication methods and security options, depending on the connection type.

Procedure

Make the following settings on the tab page:

Connection Types: ABAP, R/2, Logical, TCP/IP (2, 3, L, T)

Trust Relationship (for type 3 only) if the target system is a Trusted System, choose Yes.
- Logon screen
  Here, you can determine whether a logon screen should appear the first time the destination is called.
  
  Note
  You should not use this option with background programs.
  
  End of the note.
  
  Note
  The logon screen cannot be used together with a trusted system relationship.
  
  End of the note.

SNC (Secure Network Communications, only available for types 3 and T)
If you have an actively SNC-supported security system, you can activate security options that you must set using Edit SNC Options .
Authorization
If you enter a literal in this field, the system performs a check on the client side at runtime to check whether the caller has the relevant authorization to call via this destination. The specified literal must be entered in the caller’s authorization profile in authorization object S_ICF.
Example
- For the destination in transaction SM59, enter the following data:
  Value in field AUTHORITY of destination: "CHECK".
- In authorization object S_ICF, define the following:
  Value in field ICF_FIELD: "DEST"
  
  Value in field ICF_VALUE: "CHECK".
End of the example.
Logon
- Language
  System language to be used
- Client
  Client code
- Users
  User name to be used for remote logon, if different from current user name
- Password status
  Whether a user password has already been saved
- Password
  User password
- Current user
  The logon to the remote system should be performed using the currently logged on user name.

Connection Types: Internal, CMC, ABAP Driver (I, M, X)

Authorization
If you enter a literal in this field, the system performs a check on the client side at runtime to check whether the caller has the relevant authorization to call via this destination. The specified literal must be entered in the caller’s authorization profile in authorization object S_ICF.
Example
- For the destination in transaction SM59, enter the following data:
  Value in field AUTHORITY of destination: "CHECK".
- In authorization object S_ICF, define the following:
  Value in field ICF_FIELD: "DEST"
  
  Value in field ICF_VALUE: "CHECK".
End of the example.

Connection types HTTP/External and HTTP/ABAP (G, H)

Logon Procedure

Logon Using User
In this section you can define what type of Authentication you want to use for the destination as long as the logon is to take place with a user.
Logon with Ticket
If the logon is not to take place with a user but with a Logon Ticket then you can make the relevant settings in this section.

Security Options

Status of Secure Protocol
Here, you can determine whether to use SSL for the destination, and enter the relevant SSL client certificate if applicable.

You can also determine whether to use the SAP logon ticket for the authentication.
Authorization for the Destination
If you enter a literal in this field, the system performs a check on the client side at runtime to check whether the caller has the relevant authorization to call via this destination. The specified literal must be entered in the caller’s authorization profile in authorization object S_ICF.
Example
- For the destination in transaction SM59, enter the following data:
  Value in field AUTHORITY of destination: "CHECK".
- In authorization object S_ICF, define the following:
  Value in field ICF_FIELD: "DEST"
  
  Value in field ICF_VALUE: "CHECK".
End of the example.
Logon
- Language (HTTP/ABAP only)
  System language to be used
- Client (HTTP/ABAP only)
  Client code
- Users
  User name to be used for remote logon, if different from current user name
- Password status
  Whether a user password has already been saved
- Password
  User password
- Current user (HTTP/ABAP only)
  The logon to the remote system should be performed using the currently logged on user name.