Follow the instruction steps in this section to apply your Relying Party and SSO Agent configuration to IBM Security Access Manager Federation.
Before you begin: Configure the integration type that your use case will employ. Refer to the Integration Configuration Summary section for more information.
Procedure
1. Log in to the local management interface of the appliance.
2. Browse to Secure Web Settings > Manage > Reverse Proxy.
3. Select the reverse proxy server instance that was added in prerequisites and click Manage > AAC and Federation Configuration > Federation.
4. On the Federation Management window, click Add.
5. Add Federation to Reverse Proxy window,
- On the Main tab, click Next.
- On the Runtime tab, enter password for easuser in the Password field and click Next.
- On the Federation tab, select the federation instance from Federation drop-down list and click Next.
- On the Reuse Options tab, click Finish.
6. On the Federation Management window, click Close.
7. Deploy changes
8. Next Step is to configure Point of Contact profile to configure user access.
Configure Point of Contact Profile
1. On the local management interface, browse to Secure Federation > Global Setting > Point of contact.
2. On the Point of Contact page, select Current Profile as either,
- Access Manager Username and extended attributes to allow only known, preregistered users perform single sign-on into the service provider.
- Access Manager Credential to allow all authenticated users to sign-on to the service provider.
3. Click Set As Current.
4. Deploy changes.
Single Sign-on URL:
Use the below URL syntax to access the protected resource using federation.
https://<isam_hostname>:<port_number>/<junction_name>/sps/<federation_name>/saml20/logininitial?RequestBinding=HTTPPost&PartnerId=<provider_ID>&NameIdFormat=Email&Target=https://<target_application_location>
Where:
- isam_hostname is the host name of the reverse proxy server.
- port_number is the port number of the reverse proxy server.
- junction_name is the name of the junction configured for the reverse proxy server.
- federation_name is the name of the federation that was created on the service provider.
- provider_ID is the identity provider ID.
- target_application_location is the application that a user can log on to using single sign-on.
Example:
URL for access through Relying Party
URL for access through SSO agent
Head back to the main page for more certification related information.
Related Articles
Microsoft Office 365 – WS-Federation SSO and Hybrid Domain Join Configuration – RSA Ready Implementation Guide 94Number of Views IBM Security Access Manager 9.0 - Authentication Agent Configuration - RSA Ready SecurID Access Implementation Guide 12Number of Views Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 692Number of Views RADIUSwith AM Configuration - Cisco FTD RSA Ready SecurID Access Implementation Guide 93Number of Views Vmware vSphere vCenter 6.7 - Authentication Agent Configuration - RSA Ready SecurID Access Implementation Guide 207Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Group Policy Object Template Guide Unable to recognize the .iso file while uploading the patch through web browser from the Operations Console in RSA Authent… How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process