I’ve been trying to find documentation around SAML 2.0 support in the webMethods Integration Server adapter for SAP.
I need Integration Server (IS) to mediate between a SharePoint system and SAP. A key part of this is to enable SAP to pick up the actual user that initiated the interaction in SharePoint, not just a generic account Integration Server’s adapter might be using when communicating with SAP.
It mentions “Note: You can only use SAML tokens when using WS-SecurityPolicy. The Integration Server WS-Security facility does not support SAML tokens.”
“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.”
and
“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.
Thanks, rmg, I’m suing webMethods SAP Adapter 7.1. As you pointed out there’s support for SAML in IS and Mediator. What’s not clear to me is whether there’s SAML 2.0 support in the adapter.
Going back to my question, most likely, RFC doesn’t support SAML or an extensible authentication mechanism. If that was the case, no connector - including the one from Integration - would possibly be able to support it.
In that sense, possibly the best option would be to expose the SAP function as a Web service. Of course that loses the simplicity of using a direct SAP connector.