Publishing SAML-enabled Internal Web Application with Luminate Secure Access Cloud
In some scenarios, existing on-premises Web Applications can use SAML authentication with organizational identity provider, such as Okta, Ping Identity or OneLogin. However, usally these applications are only accessible via VPN or from the corporate network and are using an internal DNS address.
Please note, that if the intention is to keep the DNS address of the internal application after publishing it with Luminate (i.e., myapp.mycompany.com) a different procedure needs to be applied. Currently, please contact Luminate Support Team for guidance.
In our example, the Confluence application is configured with SSO using Okta (SAML based SSO) and supports both SP-Initiated and IdP-Initiated login (via the Okta hub). Naturally, the procedure below can be applied to a different web application and a different SAML IdP.
This article will provide a step by step guide on how to configure the application to be accessible via Luminate while maintaining the SSO configuration with Okta to support both SP-Initiated and Idp-Initiated.
Step 1 – Configure the application to be accessed via Luminate
First of all – let’s create a web application in Luminate to publish the confluence application.