OneLogin - SAML Integration

Use these instructions to configure your OneLogin account with WhosOffice for single sign on.

If you require any assistance with this setup please contact support@whosoffice.com

Pre-requisites

  • You will need an administrator account to access the OneLogin administration area
  • You need to have an existing account with WhosOffice
  • You will need an Administrator role on WhosOffice to complete these steps

1. Identify your sub-domain from WhosOffice

  1. Login to your WhosOffice account
  2. From the Settings menu, go to Company
  3. Make a note of your sub-domain from this page, it will be in bold as shown below.

Your company sub-domain

2. Add WhosOffice to your OneLogin account

  1. Login to your OneLogin account
  2. Ensure you are in the Administration area
  3. From the Applications menu, click on Applications
  4. On the right-hand side, click on the Add App button
  5. Search for and click on "whosoffice" in the application directory
  6. Under the configuration area, leave the Display Name
  7. You can upload a logo and icon (save the images below for convenience) to identify WhosOffice to your users
    WhosOffice icon  WhosOffice square icon
  8. Click on the Save button, top right

3. Configure your WhosOffice connector

  1. Once the connector has been added to your account, you will then need to complete the configuration
  2. Click on the Configuration link on the left-hand side
  3. You will need to supply the "System name" value, which is the sub-domain on your WhosOffice account, see Step 1.
    Configure your WhosOffice connector
  4. Click Save

4. Download your metadata file

  1. From the "More Actions" menu, click on "SAML Metadata"
    This will download the metadata file to your computer, which you will then need to upload to WhosOffice on the next step so make sure you know where this file is downloaded to.
    Download the SAML Metadata file

5. Configure your WhosOffice account

  1. Login to your WhosOffice account
  2. From the settings menu, go to Company
    Login to your WhosOffice account
  3. Click on the "Single Sign On" tab
    Enable the integrations
  4. Select "OneLogin" from the provider drop down and click on "Activate Login Provider"
  5. Using the form, browse to the SAML metadata file you downloaded in Step 4, click on Upload
    Upload your metadata file
  6. Click on Save Changes
    Note: If you would like to force users to Authenticate through OneLogin (for online logins only), make sure "Force SAML" is selected as "Yes" then click on "Save Changes".

6. Enable WhosOffice SAML connector

For details on how to specify which users are able to use the WhosOffice connector from your OneLogin account, refer to the support section within OneLogin.

7. Verify that SSO is working

  1. Ensure that you are logged out of your WhosOffice account
  2. Navigate to https://{sub-domain}.my.whosoffice.com
    Remember to replace {sub-domain} with your company's dedicated sub-domain from Step 1.
  3. If you have chosen to "Force SAML" you will be automatically redirected to the OneLogin sign-in page
  4. If you have chosen NOT to "Force SAML" you will see the WhosOffice login screen with an option to login through OneLogin
    Enable the integrations
  5. After you have authenticated your login with OneLogin you will be redirected to your WhosOffice account

 


Title: OneLogin - SAML Integration
Category: Integrations
Posted: Wednesday, 29th Jan 2020
By: Tony Bushell
Direct link: https://www.whosoffice.com/support/knowledgebase/onelogin-saml-integration


View all knowledgebase articles

Close menu Home Features Pricing Support Contact us Our blog Request Demo

Cookie settings for whosoffice.com

We use cookies to improve our website experience, we also use cookies to help us undertand how our website is used, enhance site navigation and analyze site usage and advertising. For more information please refer to our Cookie Policy.

AdvertisingEnables storage related to advertising, for example, advertising campaign.
AnalyticsEnables storage related to analytics, for example, visit duration.
TargetingSets consent for sending user data to Google for online advertising purposes.
MarketingSets consent for personalized advertising.
Manage cookies