Verify Access (Access Manager) Federation
Verify Access (Access Manager) Federation Courses:
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 cookbook provides a step-by-step guide to installing a pair of IBM Security Access Manager Virtual Appliances and then configuring them to demonstrate federation scenarios (such as federated single sign-on using the SAML 2.0 Browser POST profile) and Secure Token Service scenarios.
This cookbook is designed to work with IBM Security Access Manager 184.108.40.206.
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.
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.
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.
In this lab, you configure Access Manager V9.0.3 to facilitate
authentication to the WebSphere Liberty application using JSON Web Tokens (JWT).
IBM Access Manager also known as IBM Security Access Manager V9 supports Federation as an add-on module. In this Open Mic organized by Access Manager support team, Virag Patel talked about the administration aspect of the Federation module. You can configure and administer the Federation using the appliance console as well as the Rest APIs. Some of the key presentation topics included configuration using CLI, LMI and Rest API interfaces, supported federation types, setting up the reverse proxy (WebSEAL) instance as a Point of Contact (POC), mapping rule configuration, template files, troubleshooting and log analysis.
This video demonstrates how to create a federation partner in IBM Security Access Manager version 9.
After the presentation, attendees were given an opportunity to ask the panel of experts questions.
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).
In IBM Security Access Manager v9.0.4, a new OpenID Connect (OIDC) implementation is available where OIDC is built on top of OAuth 2.0. In previous versions, OIDC and OAuth were implemented separately, and OIDC support was limited to simple Single Sign-on use cases. In this course, you will learn about the benefits of this new implementation.