Show TOC

Background documentationConfiguring the Sender Locate this document in the navigation structure

 

For the various protocols and adapters that support principal propagation, you have to configure for which messages an SAP assertion ticket is to be created for the application user.

ABAP Proxies

For ABAP proxies, perform the following steps:

  1. Call transaction SXMB_ADMIN.

  2. Choose Configure Principal Propagation.

  3. Choose Define Interfaces.

    A table is shown, in which you can maintain entries of the following form:

    interface name, interface namespace, user

    Entries with an asterisk (*) are allowed in all fields. If you enter an asterisk only, all interfaces, namespaces, or users are considered.

Whenever at least one entry in the table matches a message execution in an ABAP outbound (sender) proxy, principal propagation is enabled for this message.

Java Proxies

For Java proxies, you have to maintain the file PP_Validate.ini. It contains the interfaces and users for which you want to activate principal propagation.

You can find this file in the directory \usr\sap\<SID>\SYS\global\xi. If it does not exist, principal propagation is switched off by default.

Create or modify the file PP_Validate.ini as follows:

  • Maintain your entries in the following form, one entry per line.

    interface namespace, interface name, user

    Entries with an asterisk (*) are allowed in all fields. If you enter an asterisk only, all interfaces, namespaces, or users are considered.

    Example Example

    NS1,N1,U1 *,*,U2 NS2,*,*

    In this example, principal propagation is switched on

    End of the example.

    • whenever interface NS1, N1 is used by user U1

    • for all interfaces used by user U2

    • for all interfaces with namespace NS2

      This means that principal propagation is switched on for at least one of these three cases.

Whenever at least one entry in the file matches a message execution in a Java outbound (sender) proxy, principal propagation is switched on for this message.

RFC Sender

RFC sender programs use two different methods to obtain the necessary information for issuing RFC calls: An RFC program uses either an RFC destination (ABAP sender system) or a property file according to the RFC library for external RFC client programs.

For each method, you should specify that an SAP logon ticket or an SAP assertion ticket has to be created for the call. In an RFC destination of type G or T, for example, there is an explicit checkbox specifying that an SAP assertion (logon) ticket should be created.

SOAP Sender

The SOAP client itself must be able to issue SAP assertion tickets. If the sender is an SAP program, an HTTP destination of type G can be used. If the sender is a SOAP (receiver) adapter, simple principal propagation can be used.

Note Note

Even if an anonymous user is used for authentication, principal propagation can still be configured in the Integration Directory, thus providing for propagation of this anonymous user.

End of the note.