Wdesk cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Wdesk

Here's how to set up single sign-on (SSO) via SAML for the Wdesk® application.

Step 1: Get Google identity provider (IdP) information
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click Add Add at the bottom right.
  4. Locate and click Wdesk in the application list.
  5. On the Google IDP Information page, download the IDP metadata file.

Leave the Admin console open, you'll continue with the configuration wizard after performing the next step in the Wdesk application.

Step 2: Set up Wdesk as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to Wdesk with your administrator account.
  3. Navigate to Admin and then Security and then Settings.
  4. Click SAML Settings and select (check) the following options:
    • Enable SAML Single Sign-On
    • SAML User ID is Wdesk username
    • NameIdentifier element in Subject statement 
  5. Click Save changes.
  6. Click Configure IdP Settings.
  7. Next to Identity Provider Metadata, click Choose File.
  8. Locate and upload the IDP metadata file you downloaded in Step 1 above.
  9. Click Save changes.
  10. In Service Provider Details, copy and save the Metadata URL and Consumer URL values, which contain your Wdesk domain name and unique customer ID. You'll use these URLs to finish SSO configuration in the Admin console in the next step.
Step 3: Finish SSO configuration in Admin console
  1. In the SSO configuration wizard, click Next.

    The Basic information window shows the Application name and Description seen by users.

  2. Click Next.
  3. On the Service Provider Details page, edit the ACS URL and Entity ID as follows:
    •  ACS URL: replace the default value with the Consumer URL value you copied from Wdesk in Step 2.
    • Entity ID: replace the default value with the Metadata URL you copied from Wdesk in Step 2.
  4. Click Next.
  5. On the Attribute Mapping page, set the Select category and Select user field values as follows for the listed attributes:
     
    Application attribute Select category Select user field
    email Basic Information Primary Email
    username Basic Information Primary Email
  6. Click Finish.
Step 4: Enable the Wdesk app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Select Wdesk.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. Ensure that your Wdesk user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working
  1. Close all browser windows.
  2. Navigate to your Wdesk instance. You should be automatically redirected to the Google sign-in page.
  3. Enter your username and password.

After your sign in credentials are authenticated, you're automatically redirected back to Wdesk.

Was this helpful?
How can we improve it?