What is your IS/SAP Adapter version and current adapter fix level?
Also some notes on SAML 2.0 from the Empower:
Please refer to “8-2-SP1_Web_Services_Developers_Guide.pdf” (http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite8-2_sp2/Integration_Server/8-2-SP1_Web_Services_Developers_Guide.pdf) starting page 159 on section “How You Can Secure SOAP Messages with WS-Security”.
It mentions “Note: You can only use SAML tokens when using WS-SecurityPolicy. The Integration Server WS-Security facility does not support SAML tokens.”
Refer to “8-2-SP2_Administering_Mediator.pdf” (http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite8-2_sp2/Mediator/8-2-SP2_Administering_Mediator.pdf) on page 46, it mentions:-
“Require WSS SAML Token
When the ?Require WSS SAML Token? policy action is set for the virtual service, Mediator uses a WSS Security Assertion Markup Language (SAML) assertion token to validate service consumers. Mediator supports SAML 1.1 and 2.0 tokens, and supports sending SAML 2.0 Sender-Vouches tokens to the native service.”
“In order to use a SAML token, Mediator requires that you:
? Determine which Security Token Services (STS) to trust. The STS generates the SAML tokens that clients will submit. The client can use any STS provider that generates SAML 1.0 or 2.0 tokens.”
Also you may check with the SAG support about SAML2.0 support for SAP Adapter side of it.