Access Manager Federation
Access Manager Federation Courses:
After the presentation, attendees were given an opportunity to ask the panel of experts questions.
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.
This video demonstrates how to create a federation setup on the identity provider in IBM Security Access Manager version 9.
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.
In this lab, you configure Access Manager V9.0.3 to facilitate
authentication to the WebSphere Liberty application using JSON Web Tokens (JWT).
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.
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.
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.
IRLP code: SEC9604
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).
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.
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.