Setting up federation with providers other than Access Manager Identity Servers requires the same basic tasks as setting up federation with Access Manager Identity Servers, with some modifications.
When you set up federation with identity providers and service providers that are controlled by a single company, you have access to Administration Consoles for both Identity Servers and know the admin credentials. When setting up federation with another company, additional steps are required.
You need to negotiate with the other company and gain approval for federation because metadata must be shared and both sites require configuration. You need to negotiate a schedule for these configuration changes.
The other site might not be using Access Manager for its identity or service provider. The basic tasks need to be modified to accommodate how that implementation shares metadata, authentication methods, and roles.
Many SAML 1.1 providers do not support a metadata URL, and the data must be imported manually.
For example, instead of sharing URLs that allow you to import metadata, you might need to share the actual metadata and paste it into the configuration. The Access Manager Identity Server validates the metadata of another identity provider or service provider; some implementations do not validate it. If Identity Server determines that the metadata is invalid, you need to negotiate with the provider to send you metadata that has been validated.
Most third-party providers do not support authentication cards and contracts. However, most do support either authentication types or authentication URIs. You can use either of these to map from their authentication procedure to an Identity Server authentication contract.
For sample implementations with third-party providers that explain the modifications that were required to set up the federation, see the following: