ISAM Federation STANDARDS AND MAPPINGS. Gabriel Bell IBM Security L2 Support Jack Yarborough IBM Security L2 Support.

Transcription

1 ISAM Federation STANDARDS AND MAPPINGS Gabriel Bell IBM Security L2 Support Jack Yarborough IBM Security L2 Support July 19, 2017

2 Agenda ISAM Federation Introduction Standards and Protocols Attribute Sources HTTP Callout Mapping Module Java Script Mapping Quick Connectors 2 IBM Security

3 ISAM Federation Introduction Federated single sign-on solution for the ISAM appliance Introduced in ISAM 9.0 as a module Runs on a WebSphere Liberty Profile instead of WebSphere Application Server Utilizes IBM Security Access Manager Reverse Proxy as a Point of Contact Currently no migration from TFIM 3 IBM Security

4 Standards and Mappings Functionality Federated Identity Manager ISAM Federation SAML Single Sign-on SAML 1.X, 2.0 SAML 2.0 OpenID Single Sign-on OpenID OpenID Connect WS-Federation WS-Federation 1.2 WS-Trust Security Token Service Security Token Service TFIMSSO Token Conversion SAML2, LTPA, IVCred, X509, Kerberos SAML2, LTPA, IVCred, JWT Attribute Mapping Partner Templates Java Script, Java STS Module, TDI, XSLT Attribute Sources, External Identify Mapping, Java Script Quick Connectors 4 IBM Security

5 Attribute Sources Credential Value obtained from the ISAM user credential (IVCred) LDAP Value obtained from an directory server Fixed Free form text value 5 IBM Security

6 Quick Connectors HEADER CONTENT 1 HEADER CONTENT 2 Partner templates used to create single sign-on with ISAM Federation Includes configuration instructions Mapping for predefined attributes required by the partner Source: Title, Published date, author, company 6 IBM Security

7 HTTP Callout Module Used to externalize identity and attribute mapping Message format can be XML or WS-Trust HTTP and HTTPS communication to external servers Can be used to call the ISAM Federation STS trust chains 7 IBM Security

8 Java Script Mapping Rules Allows administrators to customize the identity and attributes in the user credential Prior to ISAM the Default Mapping module input must be the STSUU object ISAM Federation allows access to the STSRequest and STSResponse classes Input to Default Mapping Module can now be any generic XML element This flexibility allows mapping between JWT and SAML2 STSRequest can be used to get the input security token from WS-Trust request STSResponse can used to set the output security token in WS-Trust response 8 IBM Security

9 9 IBM Security QUESTIONS?

10 THANK YOU FOLLOW US ON: ibm.com/security securityintelligence.com youtube/user/ibmsecuritysolutions Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and / or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. Statement of Good Security Practices: IT system security involves protecting systems and information through prevention, detection and response to improper access from within and outside your enterprise. Improper access can result in information being altered, destroyed, misappropriated or misused or can result in damage to or misuse of your systems, including for use in attacks on others. No IT system or product should be considered completely secure and no single product, service or security measure can be completely effective in preventing improper use or access. IBM systems, products and services are designed to be part of a lawful, comprehensive security approach, which will necessarily involve additional operational procedures, and may require other systems, products or services to be most effective. IBM DOES NOT WARRANT THAT ANYSYSTEMS, PRODUCTS OR SERVICES ARE IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THE MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY.