Give us feedback
idp
Web icon

IdP

Stable version 5.0.13 (Compatible with OutSystems 11)
Other versions available for 10 and Older
Uploaded on 19 Mar (4 weeks ago) by 
4.3
 (49 ratings)
idp

IdP

Documentation
5.0.13

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider, and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname


Optional Internal Settings:

  • Always Initiate SSO
    • When enabled, this option will force the new request to perform the authentication on the External Identity Provider even then when there is already a valid session for that user in OutSystems.
  • Skip IdPReact 
    • This setting is only visible when IdP detects an installation of the IdPReact component.
      When enabled, this option will skip the redirect to the IdPReact component and behave as if the component is not installed.
      Before enabling this setting, make sure you have the "Single Sign-On Between App Types" option enabled in Service Center
  • Encrypt URL Parameters"
    • When enabled, the intermediate redirect performed by IdP will have its values encrypted.
      Consumers of the IdP component will need to be republished to take advantage of this new option (they will default to the previous behavior otherwise).
  • Enforce Encryption of URL Parameters
    • Enforce that all requests must use the new Encryption method of sending the configuration on intermediate redirects.
      With this option enabled, all consumers of the IdP module must be republished with version 5.0.10+ of the IdP component in order to be able to generate requests using the new mechanism.


Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New Application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID)http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL)https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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


5.0.12

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider, and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname


Optional Internal Settings:

  • Always Initiate SSO
    • When enabled, this option will force the new request to perform the authentication on the External Identity Provider even then when there is already a valid session for that user in OutSystems.
  • Skip IdPReact 
    • This setting is only visible when IdP detects an installation of the IdPReact component.
      When enabled, this option will skip the redirect to the IdPReact component and behave as if the component is not installed.
      Before enabling this setting, make sure you have the "Single Sign-On Between App Types" option enabled in Service Center
  • Encrypt URL Parameters"
    • When enabled, the intermediate redirect performed by IdP will have its values encrypted.
      Consumers of the IdP component will need to be republished to take advantage of this new option (they will default to the previous behavior otherwise).
  • Enforce Encryption of URL Parameters
    • Enforce that all requests must use the new Encryption method of sending the configuration on intermediate redirects.
      With this option enabled, all consumers of the IdP module must be republished with version 5.0.10+ of the IdP component in order to be able to generate requests using the new mechanism.


Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New Application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID): http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL): https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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


5.0.11

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider, and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname



Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New Application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID)http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL)https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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


5.0.10

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider, and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname



Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New Application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID): http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL): https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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


5.0.9

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider, and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname



Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New Application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID)http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL)https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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


5.0.8

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.

Since Platform Server Release Jul.2019 CP2 (August 23rd, 2019) you can configure a SAML 2.0 authentication for the whole environment directly in the Users application. Check the documentation on how to Configure SAML 2.0 Authentication.

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 the OutSystems application of the verified identity of the user who is logging in, and the user is redirected back to the portal website.

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 behavior, and instead of redirect the user to the Login screen, redirect it to the Identity Provider.

  • 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.

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, to achieve that, it's necessary to change the Logout default behavior.

If your IdP Server allows a Logout initiated by the SP (IdP Connector), 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 shouldn't call the User_Logout or Logout system actions. The 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.

Configure IdP connector

To configure the SAML Single Sign-On in the IdP component you must 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')

Note: When updating the certificate, make sure you update it on both ends, in your Identity Provider and in OutSystems, in the IdP component.


IdP Initiated Login


When performing an IdP Initiated login, make sure you include a query parameter with the name IdpAppName with the value of the Saml App configuration to use.

  • Examples: 
    • https://yourdomain/yourmodulename/yourscreen?someparameter=somevalue&IdpAppName=yoursamlappname
    • https://yourdomain/yourmodulename/yourscreen?IdpAppName=yoursamlappname
    • /ModuleName/Screen?IdpAppName=yoursamlappname



Configure Identity Provider - Examples

Azure AD / ADFS

  1. Sign in to the Azure Active Directory portal and add the OutSystems Azure AD application from the gallery.

    • Navigate to Enterprise applications

    • Click New application.

    • Search for OutSystems Azure AD.

    • Select the application and click Add.

  2. Select SAML as the single sign-on method.

    • In the OutSystems Azure AD application dashboard click the Single sign-on entry.

    • Select SAML.

  3. Set up Single Sign-On with SAML.

    • Click the Edit icon on the Basic SAML Configuration section.

    • Set the required values accordingly.

      • Identifier (Entity ID): http://YOUR_SERVER/IdP/

      • Reply URL (Assertion Consumer Service URL): https://YOUR_SERVER/IdP/SSO.aspx

        • Alternatively, you can upload the metadata file from the IdP connector.


  4. You can then configure the IdP connector with the provided information in sections 3 and 4, or upload the Federation Metadata XML file downloaded in the Azure AD application.

Okta

  1. Create an Okta trial account.

    • Go to 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.

  2. 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.

  3. Add a SAML application to your Okta domain.

    • Access the Admin Dashboard and click to Add Application.

      • Click on the Create New Appbutton.

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

          • Define the App Name (for example, OutSystems Okta) and click Next.

  4. 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

      image alt text

      • Click on the Show Advanced Settings link and set the remaining values

      • Signature Algorithm: RSA-SHA256

      • Digest Algorithm: SHA256

    • 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.




  5. You can add the values manually or optionally save the content of the "IDP metadata" in an .XML file and upload it on the IdP configuration page:

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.

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

  5. Configure Display Name of your application and then click on Save button.

  6. Click on the Configuration tab and configure the following properties.

    • ACS (Consumer) URL Validator: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • ACS (Consumer) URL: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

  7. Click on SSO tab and configure the following properties

    • SAML Signature Algorithm: SHA-256

  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.

  4. Select New SAML Application option.

  5. Configure application name, description, category and click on Continue to Next Step.

  6. On Application Configuration configure the following properties

    • Assertion Consumer Service (ACS): URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Entity ID: URL of the OutSystems environment to handle the SAML response (http://YOUR_SERVER/IdP/SSO.aspx)

    • Signing Algorithm: RSA_SHA256

  7. Click on Continue to Next Step and then Save & Publish.

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