Verify Access (Access Manager) Federation

Verify Access (Access Manager) Federation Courses:

Configuring Verify Access as identity source for Verify SaaS

IBM Security Verify offers Single Sign-On (SSO) capability to SaaS (Software as a Service) and cloud applications such as Microsoft Office 365, Google Apps, Workday, and Salesforce. You can configure Verify Access as an identity source for Verify. This connectivity enables Verify Access users to single sign-on to Verify, and then further single sign-on to SaaS applications.

This lab provides step-by-step instructions to integrate an on-premises Verify Access system to your IBM Security Verify tenant. You use Verify Access as a SAML Identity Provider to authenticate against a corporate LDAP directory and then assert the identity information to IBM Security Verify.

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 OpenID Connect federation

This lab demonstrates how to set up the OpenID Connect federation using IBM Security Access Manager (ISAM)  9.0.7. The lab provides two Access Manager appliances: isam1 and isam2. The isam1 appliance is used as an OpenID Connect Provider (OP) and the isam2 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.

Configuring SAML 2.0 Federation

IBM Security Access Manager (ISAM) provides a Federation module so that collaborating organizations can gain secure access to each other's applications. The Federation module supports SAML 2.0 federations.

This course provides a lab setup and step-by-step instructions on how to set up the SAML 2.0 federation using IBM Security Access Manager V9.0.7. The lab provides two SAM appliances: isam1 and isam2. The isam1 appliance is used as a SAML Identity Provider (IdP) and the isam2 appliance acts as a SAML Service Provider (SP). The built-in demo application running on the Service Provider appliance is used for verifying federation capabilities.

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).


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).