Show TOC

Procedure documentationConfiguring Principal Propagation (Authentication Assertion Ticket) Locate this document in the navigation structure

 

You can configure principal propagation based on authentication assertion tickets.

Prerequisites

The sender and receiver adapters must be one of the following:

  • XI adapter

  • SOAP adapter

  • RFC adapter

Procedure

1. Configuring Back-End Systems Involved

First configure the involved back-end systems.

The basis of secure principal propagation is a trusted relationship between the involved back-end systems. You perform these steps separately in each back-end system.

For more information, see: Configuration of Principal Propagation

2. Configuring in the Integration Directory

In the Integration Directory, specify between which entities principal propagation is to take place.

If you would like principal propagation to occur between a sender and a receiver using the Integration Server, perform the following steps:

  1. Implement principal propagation from the sender to the Integration Server. In the corresponding sender agreement, on the Parameters tab page, under Settings for Principal Propagation select the Principal Propagation checkbox.

    If this checkbox is selected, the signature of the sender ticket is verified and the corresponding user can log on to the Integration Server.

    For more information, see: Defining Sender Agreements

  2. Implement principal propagation from the Integration Server to the receiver. In the corresponding receiver agreement, on the Parameters tab page, under Settings for Principal Propagation select the Principal Propagation checkbox.

    For more information, see: Defining Receiver Agreements

    Note Note

    The checkbox is only displayed if you have assigned the sender or receiver agreement a communication channel with the appropriate adapter type (for more information, see Prerequisites).

    End of the note.