Set Up Corporate Login (SSO) with OneLogin

With Corporate Login (Single Sign-OnClosed A corporate login (also Single Sign-On or SSO) allows users to sign into the TrueContext Web Portal and apps by authenticating the user's login through an identity provider (IdP), such as Okta or OneLogin. Users must initiate SSO from the TrueContext Web Portal or Mobile App., or SSOClosed A corporate login (also Single Sign-On or SSO) allows users to sign into the TrueContext Web Portal and apps by authenticating the user's login through an identity provider (IdP), such as Okta or OneLogin. Users must initiate SSO from the TrueContext Web Portal or Mobile App.), your users can sign in to TrueContext with the credentials they use for OneLogin. To set it up, you configure SSO in two places: in TrueContext, and in your identity provider. This topic covers the OneLogin side. For the TrueContext side, refer to Set up corporate login (Single Sign-On).

Available on the Intelligent and Elite tiers:

—Digital
Intelligent
Elite
?

Note:If you change the SSO settings of your OneLogin app after setup, download the OneLogin metadata file again and upload it to your team’s Single Sign-On settings in the Web Portal. This keeps authentication in sync between TrueContext and OneLogin.

Add the TrueContext app in OneLogin

  1. Sign in to OneLogin as an administrator.

  2. Select Administration.

    The OneLogin user portal. A callout on the Administration link in the top bar reads “Select Administration.”

    Result: The OneLogin administrator dashboard opens.

  3. Go to Applications > Applications.

    The OneLogin administrator dashboard with the Applications menu open, showing Applications, Portal Tabs, and Custom Connectors. A callout on Applications reads “Select Applications.”

    Result: The Applications page opens and lists your company’s apps.

  4. Select Add App.

    The OneLogin Applications page. A callout on the Add App button reads “Select Add App.”

    Result: The Find Applications page opens.

  5. Several connectors have similar names. Search for SAML Custom Connector, and then select SAML Custom Connector (Advanced).

    The Find Applications page with search results for “saml custom connector.” A callout on SAML Custom Connector (Advanced) reads “Select this option.”

    Result: The Add SAML Custom Connector (Advanced) page opens.

  6. In Display Name, enter a name that tells your users the app signs them in to TrueContext. Optionally, upload a Rectangular Icon and a Square Icon.

    The Add SAML Custom Connector (Advanced) page with TrueContext Connector entered as the display name. A callout on Display Name reads “Add a Display Name.” A callout on Rectangular Icon reads “Optionally upload an icon.” A callout on the Save button reads “Select Save when you’re done.”

  7. Select Save.

    Result: The app’s settings open, with Info, Configuration, SSO, Users, and other sections in the left pane.

  8. In the left pane, select Configuration, and then enter the values from the following table. OneLogin doesn’t accept a metadata file upload, so enter these values manually.

    The Configuration page of the SAML Custom Connector (Advanced) app, with the RelayState, Audience (EntityID), Recipient, ACS (Consumer) URL Validator, ACS (Consumer) URL, Single Logout URL, and Login URL fields. A callout on Configuration in the left pane reads “Select Configuration.” A callout on Application details reads “Enter the values from the table.”

    The Audience (EntityID) value is the entityID attribute on the md:EntityDescriptor element in your TrueContext service provider metadata file. Copy it exactly. To get the file, follow the steps in Get Service Provider Metadata from TrueContext.

    If you plan to launch TrueContext directly from OneLogin, use the values in the Launch from OneLogin column. For more information, refer to Launching Corporate Login directly from an Identity Provider.

    Field Value Launch from OneLogin
    RelayState Leave blank Leave blank
    Audience (EntityID) The entityID value from your service provider metadata file The entityID value from your service provider metadata file
    Recipient https://live.prontoforms.com/saml/SSO https://live.prontoforms.com/saml/SSO
    ACS (Consumer) URL Validator ^https:\/\/live\.prontoforms\.com\/saml\/SSO$ ^https:\/\/live\.prontoforms\.com\/saml\/SSO$
    ACS (Consumer) URL https://live.prontoforms.com/saml/SSO https://live.prontoforms.com/saml/SSO
    Login URL Leave blank https://live.prontoforms.com/security/login/saml?domain=<SSO team domain>

    In the Login URL, replace <SSO team domain> with your team’s Team Domain. For more information, refer to Team Domain.

    Note:TrueContext doesn’t support single logout. When users sign out of OneLogin, they stay signed in to TrueContext, so leave Single Logout URL blank.

    Info:We’re now TrueContext.

    • To support existing integrations, some items will continue to use “prontoforms” or “pf” in the domain or code.

  9. Select Save.

    Tip:You don’t need to change the Parameters settings. Their default configuration is correct for TrueContext.

  10. In the left pane, select SSO.

  11. To download the OneLogin metadata file that TrueContext needs, select More Actions > SAML Metadata.

    The SSO page of the SAML Custom Connector (Advanced) app with the More Actions menu open. A callout on SSO in the left pane reads “Select SSO.” A callout on SAML Metadata in the menu reads “Select SAML Metadata.”

    Result: OneLogin downloads the metadata file.

  12. In the left pane, select Users, and then add the users who sign in to TrueContext with Corporate Login.

  13. Save the app.

  14. In the Web Portal, upload the OneLogin metadata file in the Metadata File field of your team’s Single Sign-On settings. For more information, refer to Identity Provider Metadata.

Tip:To test the OneLogin app, sign out of OneLogin, and then sign in to TrueContext with Corporate Login. For more information on the sign-in steps, refer to Log in Using Corporate Login/Single Sign-On.

Related topics