How to Configure Liferay DXP with Multiple IdPs (OKTA via SAML and OIDC)

This article documents the way to configure Liferay DXP 7.x as a Service Provider working with two SSO protocols (Okta using SAML 2.0 and Google OpenID Connect). The basic configuration can be achieved within Liferay out of the box, but extra custom code is required to make it fully functional.  Both aspects are described in this article.

Basic Configuration

Okta – Liferay integration using SAML 2.0

Okta as an Identity provider and Liferay DXP as a Service Provider.

Step 1 - Okta Account Creation

  1. Create a test Okta account by clicking this link It will navigate to the Okta website.
  2. After providing the required details, the entered email address will be notified for Okta developer account Activation. By clicking Activate your account it will activate the account and navigate to Okta developer console.

Step 2 - Creation of Application in Okta

  1. On the left menu, click on Applications -> Applications > Create App Integration > Check SAML 2.0 (Since we are using SAML to integrate)
  2. Edit SAML integration will come up. In General Settings, provide the app name and upload the logo if you want to display it for your application then check the app visibility based on your use case and click Next.
  3. This will move you to the Configure SAML page. Below are some important fields which are required to configure.

  4. Click on Show Advanced Settings and select settings accordingly based on your needs.

  5. Configuring Attribute is not needed until the user sync is required. In that case, we have to configure the necessary attributes required by Liferay to import the user from IdP to SP.

  6. Leave the remaining settings as is and then click Next.
  7. In Feedback, select the second checkbox for the option Are you a customer or partner and then click Finish.
  8. By clicking Finish, the Service Provider (Liferay) configuration on the IdPs end (Okta) is successfully completed. Now we need to take the IdP’s Entity ID and Metadata to configure at SP’s end. To get the same, navigate to Application and click on the application (Liferay) we have created and navigate to Sign-On option.
  9. Click on View Setup instructions to download the metadata and to see the Entity ID.
  10. Identity Provider Issuer is the Entity ID and copy the metadata and save it as metadata.xml in order to upload into the Liferay Identity Provider connections. With this step application creation is complete.

Step 3 - User Creation in Okta

  1. Go to Directory > People > and click on Add person
  2. Once you enter the details, the respective email address will be notified for account creation activation.
  3. Clicking Activate Okta Account will create an account. Once the account is successfully created, we have to assign the respective user to the application (Liferay) which we have created inside Okta.
  4. To do the same, clicking on the respective user and clicking on Assign Application will help to assign the user to the respective application.

Step 4 - Liferay Configuration

  1. Start a vanilla Liferay DXP 7.3 bundle
  2. Go to Control Panel > Security > SAML Admin > General and set the SAML Role to Service Provider, and Entity ID to liferaysp.
  3. Create certificate.
  4. In Service Provider tab, keep the default settings.
  5. In Identity Provider Connection tab, set the following: (Remember to upload Okta’s metadata file)

  6. Go back to the General tab and enable the Service Provider.
  7. Add Sign-In portlet to home page (In case the SSO is not working, administrator can sign into portal bypassing SSO).
  8. Open a new browser and click Sign-In on the top-right which will redirect user to Okta sign-in page.
  9. Fill in the username and password.
  10. Users will be redirected back to Liferay home page and automatically sign-in.

Google OpenID Connect

Step 1 - Register Liferay DXP as an OAuth 2.0 Client in Google APIs

  1. Go to
  2. If no project exists, create a project.
  3. Refer to documentations from For example:
    1. Click Create credentials > OAuth client ID
    2. Specify Authorized redirect URIs for your application:
    3. Obtain the OAuth credentials (client_id and client_secret) generated by the Google platform.

Step 2 - Liferay Configuration

  1. Configuring an OpenID Connect Provider Connection:
    1. Go to Control Panel > Configuration > System Settings > Security > SSO and select OpenID Connect Provider under the System Scope and follow these steps:
      1. Add the provider by clicking the Add button.
      2. Use the information you received from the provider to fill out the form:
        • Provider Name: This name appears in the Sign-In Portlet when users use OpenID Connect to login.
        • OpenID Client ID: Provide the OAuth 2.0 Client ID you received from your provider.
        • OpenID Connect Client Secret: Provide the OAuth 2.0 Client Secret you received from your provider.
        • Discovery Endpoint: The rest of the URLs are obtained through this end-point. It's coming from your OpenID Connect Provider. For example:

  2. Enable OpenID Connect authentication on DXP
    1. Go to Control Panel > Configuration > System Settings > Security > SSO and select OpenID Connect under Virtual Instance Scope.
    2. Click the Enabled check box, and then click Save.

      : You can also enable OpenID Connect authentication for the given virtual instance through the Control Panel → Configuration → Instance Settings → OpenID Connect tab.

  3. Access your portal (for example
  4. On the Sign-in portlet of the home page, click on the OpenID Connect link
  5. The default Google OIDC is in the list
  6. Click on the Sign-in button: this will take you to the Google Sign-in page
  7. Enter your credentials as usual
  8. You should be redirected back to the home page after successful login

Suggested Custom Code


  1. Requesting private pages as guest always results in a SAML login
  2. Previously OIDC authenticated users (for example with expired sessions) will go via SAML login
  3. More generally, any request to /c/portal/login will go via SAML
  4. Rendering the login portlet when SAML is enabled requires some modifications.


Implement com.liferay.saml.runtime.servlet.profile.SamlSpIdpConnectionsProfile#isEnabled in a @Component. This is invoked whenever the LoginAction (/c/portal/login) is called, and it is provided with the HttpServletRequest object. It will be invoked once for each configured SAML IDP connection (also provided). If all invocations return false, then the normal login portal will render. So long as you've enabled that on the SAML Admin "Service Provider" tab.

This might be sufficient if the SAML or not-SAML decision is based on staff or not-staff. Because staff requests are likely to be coming from a known subnet. Or alternatively the fronting webserver might be able to tag the HTTP request somehow (header for example).

If more per-user control is needed, then a good approach might be to channel the potential SAML logins via the login portlet also. To achieve that com.liferay.saml.runtime.servlet.profile.SamlSpIdpConnectionsProfile#isEnabled could return false whenever a special "useSAML" (arbitrarily named) HTTP request parameter is not present.

This will then cause the login portlet to always render, and you could then register a DynamicInclude to add a "SAML" link similarly to how OpenId Connect does it. That link would need to be to /c/portal/login?useSAML . When clicked, it would cause a redirection to the SAML IdP, or present the user with a SAML IdP selection, when multiple are available.

Logout also works fine, because it checks for an active SAML SP session prior to requesting logout from any SAML IdP.

Was this article helpful?
4 out of 5 found this helpful