Skip to main content
OutSystems

How to configure OutSystems to use identity providers using SAML

Federated SSO Authentication using SAML

In order to set up a Federated Authentication in your OutSystems applications, using the SAML protocol to connect to external identity providers you can take advantage of the IdP Forge component, a generic federated identity provider (IdP) connector. IdP allows your OutSystems applications to integrate with single sign-on (SSO) provided by most of the commercial Identity Provider companies.

With this integration, when the users access an OutSystems application (Service Provider - SP), they are redirected to a web page (known as the enterprise's login manager) where they are prompted to enter their enterprise user name and password. Upon verification of the user’s login, the enterprise identity provider informs OutSystems application of the verified identity for the user who is logging in, and the user is redirected back to the portal website.

SAML_Requests.png

To successfully establish the connection between the IdP component and the Identity providers you'll need to change the authentication flow and configure both parties to redirect the user to the Login of the Identity Provider. In this article, we'll guide you through the needed setup.

Configure your application to use IdP connector

Login Flow

  • Change NoPermission screen on Common Flow. 

In a standard OutSystems application there is a Common Flow responsible for handling authentication and exception.
One of the scenarios is when a user tries to access a resource that requires the user is authenticated, and the user is not authenticated yet.
In that case, the application raises a Security exception that will be handled in Common flow and then redirects the user to the login screen.
So, the first step to integrate an OutSystems application to change this behaviour, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  1. Change Preparation of the NoPermission screen to redirect the user to the URL provided by IdP_SSO_URL action.

Note: if the system contains multiple tenants, the tenant switch has to have been done before calling IdP_SSO_URL.

Redirect user to the Identity Provider in the Preparation of the NoPermission screen

Logout Flow

  • Change LoginInfo web block on Common Flow (Optional: Single-logout).

In a standard OutSystems application the Common Flow is also responsible for handling Logout operation.
By default, the Logout will invalidate the session on the OutSystems application server, but with an IdP SSO scenario many times the logout must be also performed on IdP Server, redirecting the browser to a specific URL on IdP SSO server.
So, in order to achieve that, it's necessary to change the Logout default behaviour.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), then configure the field IdP server Single Logout URL which should be provided by your IdP Server (the IdP Connector will generate the SAML messages to perform a Single-Logout).

Note: Your application should not call the system actions User_Logout or Logout. IdP connector is the one responsible for that call.

  • Change Preparation of the LoginInfo to redirect the user to the URL provided by IdP Server
  • If your IdP Server allows a Logout initiated by the SP through SAML messages: call the action IdP_SingleLogout_URL and call the Common\ExternalURL with its output.

Change logout flow to perform logout in the Identity Provider server

 

Configure IdP connector

To configure the SAML Single Sign-on in the IdP component you will need to set up the values according to your Identity Provider.

  • IdP Server Issuer/Entity ID: A URL that uniquely identifies your SAML identity provider (IdP Server). SAML messages sent from IdP server must match this value exactly in the <saml:Issuer> attribute of SAML message.
  • IdP server Single Sign-On URL: The URL that IdP Connector should redirect to allow a user to sign in.
  • Certificate: The X.509 public certificate issued by your identity provider. Used to check the signature of SAML messages from the IdPServer.
  • SP Issuer/Entity ID: SAML Service Provider Issuer (SP Entity ID) sent in SAML messages from the IdP connector.

Optional (when required):

  • IdP server Single Logout URL: Identity Provider Server Single Logout URL. Used when the server allows SingleLogout initiated by the SP.
  • IdPConnector (SP) Keystore: The keystore that contains the private key and the public certificate that IdP connector uses to sign SAML messages sent to IdPServer (also to decrypt assertions if encrypted by IdP server). PFX/PKCS12 is the supported format.
  • KeyStore password: Keystore password to protect the keys in it.
  • Session_Cookie (site property):  Variable that holds the cookie name that has the SessionId of the IdP connector (usually 'ASP.NET_SessionId')

Configure Identity Provider - Examples

Okta

  1. Create an Okta trial account.

  • Go the Okta website and sign up to create a trial account using your company email address.
  • You should then receive an email with your account details.

  1. Sign-in to your Okta domain.

  • Access your Okta domain homepage, as described in the email.
  • Input your username and password and click Sign In.

  1. Add a SAML application to your Okta domain.

  • Access the Admin Dashboard and click to Add Application.

  • Click on the Create New App button.

  • Select Web and SAML 2.0 because we are creating a SAML integration for web applications. Click Create to continue.

  • Define the App Name (e.g.: OutSystems Okta) and click Next

  1. Configure the SAML settings for the integration.
  • Set the Single sign on URL (URL in the OutSystems environment to handle the SAML response)

http://YOUR_SERVER/IdP/SSO.aspx

  • Set the Audience URI (SP Entity ID)

http://YOUR_SERVER/IdP/SSO.aspx

  • Click on the Show Advanced Settings link and set the remaining values
  • Digest Algorithm: SHA1
  • Signature Algorithm: RSA-SHA1
  • Assertion Signature: Unsigned

  • Click Next and you’ll be asked for some information for feedback purposes. Select the option I'm a software vendor. I'd like to integrate my app with Okta and click Finish to complete the configuration.
  • Finally, click View Setup Instructions to get the data needed to configure the IdP connector.

clipboard_eab543d35593ea9ea4a2d855c820de43b.png

OneLogin

  1. Create a free OneLogin account.
  2. Log in to the admin console.
  3. Click on Apps tab then click on Add App button.

onelogin_newapp.png

  1. Search for SAML and select SAML Test Connector (IdP) option.

onelogin_samlapp.png

  1. Configure Display Name of your application and then click on Save button.
  2. Click on the Configuration tab and configure the following properties.

onelogin_configure.png

  1. Click on SSO tab and configure the following properties
  • SAML Signature Algorithm: SHA-1

onelogin_configure (1).png

8. Finally, configure the IdP connector with the provided information.

PingOne

  1. Create a free Ping Identity account.
  2. Log in to the admin console.
  3. Click on the Applications tab then click on Add Application button.

pingone_addapp.png

  1. Select New SAML Application option.
  2. Configure application name, description, category and click on Continue to Next Step.

pingone_config1.png

  1. On Application Configuration configure the following properties

pingone_config2.png

  1. Click on Continue to Next Step and then Save & Publish.
  2. Finally, configure the IdP connector with the provided information.

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and create your own application following the steps described in the Microsoft Azure documentation.
    Azure AD New Application.png
  2. Select SAML as the single sign-on method.
    Azure AD single sign-on method.png
  3. Set up the basic SAML configuration.

Azure AD - Setup Basic SAML Configuration.png

  • Alternatively, you can just upload the metadata file from the IdP connector.
    Azure AD - Upload metadata file.png
  1. You can then configure the IdP connector with the provided information on sections 3 and 4 or just uploading the Federation Metadata XML file.
    Azure AD - Set up OutSystems.png
  • Was this article helpful?