Using Okta with Central

    Here's how to integrate Central with Okta:


    Before proceeding, you must have a live Okta Identity Provider (IdP) environment.

    A live IdP environment must be configured before implementing federated authentication for Central. See Okta's Customer Success Center.

    Important: You can log in with Single Sign On on the website only. The Client App does not support Single Sign On login.
    Note: Central requires SAML 2.0 for Single Sign-On authentication. SAML 1.1 is not supported.

    Configure GoTo as a Service Provider

    The Identity Provider must be configured to trust Common Login Service (CLS) as a Service Provider. CLS is GoTo's own shared authentication service that provides single login experience for GoTo products and services on many platforms.

    You must add CLS as an application in Okta to allow a trust relationship to be established between your network and Central.

    1. Log into your Okta account.
    2. Click Admin in the upper right corner to open the administrative options.
    3. On the Applications tab, click Add Application.
    4. Click Create New App.

      The Create a New Application Integration dialog is displayed.

    5. Select SAML 2.0 and click Create.
    6. Input all data in the App Settings wizard as shown in the table below.
      Field Input or Action
      App Name Enter a unique name for CLS
      App logo

      Upload a logo for the CLS application (optional)

    7. Click Finish.

      The SAML Settings screen is displayed.

    8. Input all data in the (A) SAML Settings wizard as shown in the table below. If not specified, leave the other configuration fields empty.
      Field Input
      Single sign on URL

      Note: Leave the Use this for Recipient URL... checkbox selected.
      Audience URI (SP Entity ID)
      Note: Must be unique across all applications.
      Name ID format EmailAddress
      Application username Okta username

    Configure CLS attributes

    A unique identifier attribute must be configured. The identifier represents the shared identifier between the Identity Provider (IdP) and the host, allowing users to access services.

    Note: The identifier can include any string value.
    1. Add the following attributes under Attribute Statements by clicking Add Another. Leave the Name format option Unspecified.
      Name Value
      Email ${}
      FirstName ${user.firstName}
      LastName ${user.lastName}
    2. Click Next.
    3. Select This is an internal application that we created.
    4. Click Finish.

      The Sign On tab is displayed.

    Provide information to GoTo

    Once the IdP configuration is complete, you must provide the information listed in this section to your GoTo representative.

    Note: If you do not have an account representative, please contact us by selecting Contact Support in this article.
    1. On the Sign On screen, click View Setup Instructions.
    2. Download the following pieces of information and send them to your GoTo representative.
      Information Instructions
      Certificate Click Download certificate under step 3.
      Note: The X.509 certificate is used to encrypt and sign SAML 2.0 assertions.
      IDP Metadata Save the content under Optional.
      Note: The metadata document describes the endpoint addresses for communication.

      Once your GoTo representative has configured the SAML 2.0 connection using the information provided, your users gain access to the appropriate GoTo account and permissions via the IdP as the authentication source. It may take up to 30 minutes for the SSO service to be established for the first time.

    Article last updated: 19 October, 2022