WS_AAE Adapter

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)

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

*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) .