Latest version: v2.46

oAuth Configuration Guide

OAuth is an open standard for authorization, commonly used as a way for Internet users to log in to third party websites using their Google, Facebook, Microsoft, Twitter, One Network, etc. accounts without exposing their password. Generally, OAuth provides to clients a "secure delegated access" to server resources on behalf of a resource owner.

Also called, 2 factor authentication(2FA), multifactor authentication(MFA).

Be aware that when configuring oAuth, Exchange Autodiscover will not work. The Exchange server url must be set manually https://outlook.office365.com/ews/exchange.asmx.

 

Before you can start with the configuration of Single Sign On in Workspace 365, you need to create an app in Azure. Click the link below to check the configuration steps.

Click here for the new portal

Click here for the old portal

 

Configuring oAuth in Workspace 365

oAuth can be configured for an existing Workspace environment and a new Workspace environment. For a new environment, this is done at the second step of environment registration.

Note: Configuring oAuth when creating a new environment can only be done if you did not order Workspace 365 using an ordering platform (e.g. Odin). If you did, please follow “existing environment” setup.

In both cases, the following control will appear:

  • Switch “Single sign-on type” to oAuth2 to see oAuth settings.
  • Fill the Authority field with the according URL. It should look like this: https://login.windows.net/{TenantName}/.
  • Where {TenantName} is received at Step 2 of chapter “Configuring oAuth in the Azure Active Directory”.
  • In this case, the Authority is: https://login.windows.net/ndawqa16.onmicrosoft.com/

  • Fill in the Client ID and Key field with the according values, which you received at Step 14 of chapter “Configuring oAuth in the Azure Active Directory”
  • Now click the “Verify” button. If a page with a green background appears (verification successful) you can check the checkbox and click “Done”: 

    oAuth configuration is now complete.

 

 

Have more questions? Submit a request

Comments