Scenario After you have enabled your NetWeaver ABAP system to be an SAML 2.0 Service Provider you want to download its metadata and get an error message: 403 Forbidden. Tx: SAML2 Call the SAML 2.0 configuration Web Dynpro app via transaction SAML2 and click on Metadata. Select what to include Read more…
This is the introduction blog on how to activate SAML 2.0 based logon on SAP NetWeaver ABAP systems. The example configuration shown here is using SAP Gateway. It is the same procedure for any SAP NetWeaver ABAP system that allows SAML 2.0 logons. The system used while writing the blog Read more…
As SAML 2.0 depends on trust, it is necessary to establish this trust by exchanging the metadata of the IdP and SP. When the SAML 2.0 client for Gateway (NPL001) was created, the metadata of the Gateway SP was important to Keycloak. In this step, the metadata of the IdP Read more…
In this step a new SAML 2.0 client is created in Keycloak by importing the Gateway SP metadata. After activating and configuring SAML 2.0 in Gateway, a Service Provider (SP) was created. A metadata file for that SP is available at the saml2 Web Dynpro ABAP application. This metadata file Read more…
Before you can start to configure SAML 2.0 in SAP NetWeaver ABAP, SAML 2.0 support must be activated. The saml2 Web Dynpro ABAP app is used for this. In the NPL Developer Edition system the app is activated by default and can be accessed by opening this URL in the Read more…