Skip to Content

WS_AAE Adapter – SAML

In this blog we will see how to configure WS_AAE adapter (Sender) for SAML.

WS_AAE Adapter supports SAML 1.1 – Sender Vouches

For more information please refer below links to get head around SAML (old but good one)…

Single Sign on for Web Services – Security and Identity Management – SCN Wiki

You would have three different role players in a Web Services SSO with SAML scenario:

  • WS Consumer – User authenticates at the Token Issuer (STS) and requests a SAML Token with the WS-Trust protocol. Uses its private key to create a signature over the SAML Token and the message body
  • STS (Token Issuer) -Token Issuer authenticates the User and issues a SAML Token in the response to the WS Consumer with the WS-Trust protocol
  • WS Provider – To confirm the WS Consumer identity, WS Provider verifies the signature and compares the identity information in the SAML Token with the identity information of the WS Consumer’s Public Key certificate

Sender Vouches.pngSender Vouches

*Source – SIM 207  (link)

In this scenario we will configure SOAP UI which plays WS Consumer and STS Role and SAP PO plays WS Provider Role.


Follow below steps to establish trust relationship between WS Consumer (Soap UI) and WS Provider (PO)

  • Generate Key Pair for SOAP UI (soap UI support JKS key store format) ( You can use any key generation tool keystore-explorer)
  • Export Public Key Certificate
  • Import the Public Key Certificate into NWA – Configuration – Certificates and Keys – WebServiceSecurity  (Key storage View)

Setting Up soapUI to generate SAML Token (STS) and Sign the SAML Token and Message (WS Consumer)

  • Create a SoapUI Project
  • Create WS Security Configuration
    • Select your project and right click, select “Show Project View” from context menu
    • Select “WS-Security Configuration” Tab
      • Import Key Store (jks) file with key pair (* you need to enter the keystore password) .


      • Select “Outgoing WS-Security Configuration” Tab and click on “+”

                                  Outgoing WS-Configuration.png

      • Enter a Unique name

                                      Outgoing WS Config Name.png

                                          Outgoing WS Config Name2.png

      • Click on “+” and add sequence of configuration steps

                                        1. Timestamp (optional)

                                        2. SAML

                                        3. Signature




      • Configure Authorization for the project




                                                              Done with SoapUI configuration

  • Create a PO scenario with WS_AAE sender adapter
      • Configure sender communication channel




Once you done with configuration of ICO , you are ready to test

end point for soapUI : https://<host name>:<port>/WSAdapter/<Custom Endpoint Address>

Configuring the Sender WS Adapter – Advanced Adapter Engine – SAP Library

You must be Logged on to comment or reply to a post.
  • Hi Gov,

    Excellent blog on the interesting topic how to use SAML in SAP PO/AEX. Expecting more blogs from you and i can proudly say i learnt new topic after reading your blog.

    Keep Blogging.Good Luck.



  • I'm trying to follow this procedure. But I'm getting the following error message: "Certificate validation failed: Path does not chain with any of the trust anchors"
    Could you further detail the certificate settings within SAP PI?
    I put the public key of the certificate used in the SOAP UI, inside the Certificates and Key: Key Storage ("Trusted CAs" and "WebServiceSecurity")
    Is It Necessary to do some configuration in Trusted Systems: SAML Web Services Security?

    Some links referenced in the blog are broken


      • Now , my problem is propagate principal to RFC Receiver.

        Error: MP: exception caught with cause error while processing message to remote could not get a client from JCO.Pool:$Exception: (103) RFC_ERROR_LOGON_FAILURE: Foi recebido um SSO-Ticket não interpretado

        Can you help me?


  • I'm trying to create a .NET application to consume a webservice in SAP PI NW 7.5, but using ADFS 3.0 as STS. Has anyone done this scenario yet? I'm having trouble making the correct settings in ADFS. Using this scenario with SOAP UI is working, but with ADFS I have received some error messages. ADFS is not sending the "send voucher" as a confirmation method. It is not sending the user id. Is it necessary to register the .NET application server certificate in SAP PI, or only ADFS?