Some time ago I wanted to add a new mount point for Docker files in Proxmox. As Proxmox uses logical volumes to manage its storage, I had to find out how to assign a 200 GB part out of the Read more…
From time to time I have to create a PKI with a root and intermediate CA. As I do not want to have to search for the correct commands, I created a setup for OpenSSL and a Jupyter notebook that Read more…
In this blog I’ll show how to bring a legacy solution to the cloud. As an example, I’ll use a user management solution based on a 3-tier application: backend, middleware, frontend. Through a series of blogs, I will bring this 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 Read more…
Die DSAG Technologietage 2020 in Mannheim sind jetzt schon – leider – seit ein paar Tagen beendet. Genug Zeit die Menge an Informationen etwas im Rückblick und Abstand betrachten zu können. Mein Fokus in diesem Blog ist die SAP Fiori Read more…
After establishing the trust between the SAML 2.0 IdP and SP and activating the IdP in SAP Gateway, the ABAP system is configured for SAML 2.0 logons. An easy way to test if SAML 2.0 is working is to log Read more…
Current state is that a trust between Gateway as SP and Keycloak as IdP is established. While the previous step established the trust, the IdP is not enabled in SAP Gateway. Meaning that SAML2.0 logons are not possible. For this Read more…
This is the final step of the task to establish a trust between SAP Gateway and Keycloak. The Keycloak SAML 2.0 IdP Metadata file downloaded in previous step is now imported into SAP Gateway as a IdP. This creates the 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 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 Read more…