Access Manager Federation

Access Manager Federation Courses:

Configuring SAML 2.0 federation using IBM Access Manager

This lab demonstrates how to configure federated single sign-on (SSO) using SAML 2.0 protocol in IBM Access Manager.


Version 1.1

IRLP code: SEC9721

Configuring SSO to WebSphere Liberty using JSON Web Token (JWT)

In this lab, you configure Access Manager V9.0.3 to facilitate authentication to the WebSphere Liberty application using JSON Web Tokens (JWT).


Configuring Google as OpenID Connect Identity Provider for IBM Access Manager

This lab demonstrates how to enable social login to a web application using Google credentials. You set up OpenID Connect (OIDC) Federation for this integration because Google is fully compliant with OpenID Connect and has a metadata URI. You configure Google as an OIDC Provider and IBM Access Manager as a Relying party.
The integration scenario is demonstrated using the built-in live demo application in Access Manager.

Configuring SAML 2.0 Federation using IBM Access Manager

This course provides a lab setup and step-by-step instructions on how to set up the SAML 2.0 federation using IBM Access Manager. You configure one of the Access Manager appliances as a SAML 2.0 Identity Provider and another one as a SAML 2.0 Service Provider.

The built-in demo application running on the Service Provider appliance is used to verify federation.

Configuring OpenID Connect Federation Using IBM Access Manager

IBM Access Manager Version 9.0.4 provides new features and extended functions for OpenID Connect (OIDC). The configuration and management tasks for the OIDC Providers and Relying Parties are enhanced. You configure the OIDC Provider through the API Protection interface. Relying Party federations use a new federation wizard that supports capabilities that complies with the OIDC specifications.
This lab demonstrates how to set up the OpenID Connect federation using IBM Access Manager 9.0.4. The lab provides two AM appliances: iam1 and iam2. The iam1 appliance is used as an OpenID Connect Provider (OP) and the iam2 appliance acts as a Relying Party (RP). The live mobile demo application running on the Relying party appliance is used for verifying the federation capabilities.

Version 1.0

IRLP code: SEC9604

SAML Single Sign-On to Salesforce.com using IBM Access Manager

This lab provides step-by-step instructions for configuring a basic identity federation deployment between IBM Access Manager and Salesforce.com using SAML 2.0.
In this lab, you first obtain a Salesforce Developer Edition instance and configure it for SAML Single Sign-On from IBM Access Manager. Access Manager acts as a SAML 2.0 Identity Provider (IdP) and Salesforce acts as a Service Provider (SP).

Integrating Access Manager with Cloud Identity using Cloud Identity Connect

This lab provides a step-by-step guide to integrate an on-premises IBM Security Access Manager system to your IBM Cloud Identity tenant. You basically use Access Manager as an Identity Provider to authenticate against a corporate LDAP directory and then assert the identity information to IBM Cloud Identity and the SaaS applications supported in the Cloud Identity platform.

Using authentication services provided by Cloud Identity Verify in Access Manager

IBM Cloud Identity Verify provides Authentication-as-a-Service (AaaS). This lab provides a step-by-step guide to integrate an IBM Security Access Manager system with the Authentication as a Service (AaaS) capabilities of your IBM Cloud Identity tenant.