After you have specified the entity type, configure the details of the entity. For a local entity, define the following information:
Be aware of the following concepts:
If the Entity ID represents a remote partner, the value must be unique. If the Entity ID represents a local partner, it can be reused on the same system.
The Entity Name identifies an entity object for in the Federation Manager database. The Entity Name must be a unique value. This value is for internal use only; the remote partner is not aware of this value.
Note: The Entity Name can be the same value as the Entity ID, but the value cannot be shared.
For signing and encryption features, you must have the appropriate key/certificate entries in the database. If you do not have the appropriate key/certificate entries, click Import to import a private key/certificate pair from a file on your local system. You can also import trusted certificates.
Note: If you are using SAML 2.0 POST profile, signing assertions is required.
You can configure the asserting party to include specific assertion attributes when it generates an assertion. The recommended method is to define these attributes at the entity level. The entity serves as a template for the partnership so any assertion attributes you define for the entity get propagated to the partnership. The benefit of defining assertion attributes at the entity is that it enables you to use an entity in more than one partnership.
If you want to add or remove assertion attributes for the partnership, make such modifications at the partnership level, not at the entity level.
Follow these steps:
Note: Click Help for a description of fields, controls, and their respective requirements.
The Confirm dialog is displayed.
| Copyright © 2012 CA. All rights reserved. |
|