Federation Manager Guide › Federation Partnerships › Partnership Identification

Partnership Identification

After you have selected the partnership type, specify the partnership name and identify the local and remote entities.

Note: Click Help for a description of fields, controls, and their respective requirements.

Follow these steps:

1. Type the name of the partnership. You can use alphanumeric characters, underscores, hyphens, and periods in the name. Spaces are not allowed.
2. (Optional) Type a description.
3. Select a local entity from the local list if you have already configured an entity. If not, click Create Local Entity.
4. Select the remote entity from the remote list if you have already configured an entity. If not, click Create Remote Entity.

   Note: This step can be deferred if you are planning to create the remote entity by importing metadata at a later time.

5. (Optional) Enter the Skew Time in seconds.

   The skew time is the difference between the system time on the local system and the system time on the remote system. Usually, the inaccuracy of system clocks causes this condition. Determine the skew time number by subtracting the number of seconds from the current time.

   SiteMinder uses the skew time and the SSO validity duration to determine how long an assertion is valid.

6. Select one or more user directories from the Available Directories list and move them to the Selected Directories list.

   If you configure only one user directory, that directory is automatically placed in the Selected Directories list.

7. (Optional) Specify time and IP address restrictions for the partnership.
8. Click Next to move to the next step.
   • If the local entity is the asserting party (Producer or IdP), the next step is defining Federation Users.
   • If the local entity is the relying party (Consumer or SP), the next step is to configure User Identification.

Note: If you are editing a partnership, you can click Get Updates next to this field to update the entity information. The latest information from the entity configuration is propagated to the partnership. However, if you edit the entity information directly from the partnership, the changes do not get propagated back to the individual entity configuration.

More information:

Assertion Validity for Single Sign-on