...
- Start the Locator Management Console
- Go to Connections → Connector Feed
- Verify that the Azure AD connector is not currently installed by selecting the ViaWorks.Connector.AzureAD from the list. It should displayed 0 as the installed version.
- Press the Install button, this will download the installer for the connector.
- Accept the license terms and conditions and press Install
- Now that the connector is installed, let's go to Connections → Azure AD
- Add a new connection
- Name the connection Azure AD
- Fill in your full tenant name, i.e. contoso.onmicrosoft.com. Then fill in your Azure AD APP details with client ID and client secret, and the details for your service account and press Next.
- On the final page of the wizard, we select which authentication system is to be the primary, select Azure AD in the dropdown and press Finish.
- Start a CMD session with administrative privileges and perform a restart of IIS by issuing the command iisreset
...
| Info | ||
|---|---|---|
Please note If Multi Factor Authentication is enabled for additional security for the Office 365 tenant, authentication will fail in Locator, as MFA is not currently supported. If MFA is enabled, you need to have your Office 365 tenant administrator whitelist the public IP used by the server Locator is running on. If you are unable to log on after you have followed the above steps and see this in your w3wp.exe.log file:
It is very likely that Multi Factor Authentication is enabled, and a whitelist entry has to be made. |
Other references
/wiki/spaces/CONNECT/pages/593428483
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...