Has anyone successfully configured the External Provider login using Azure AD? The documentation is lacking and I would like some better instructions about the specific Configuration Information needed to get this to work. Any help in this matter would be greatly appreciated.

I have currently set up a new App Registration in Azure Active Directory. I have generated the Key and Granted Permissions. I have used the following information for the Configuration in the OAuth2 settings.

ClientID====================Application ID from Azure
ClientSecret================Key Generated from App Registration
AccessCodeServiceUri========Auth 2.0 Authorization Endpoint
AccessTokenServiceUri=======OAuth 2.0 Token Endpoint
UserInfoServiceUri==========OAuth 2.0 Authorization Endpoint
ResourceID==================Application ID from Azure
UserInfoIDPath==============?? (upn)
UserInfoEmailPath===========?? (upn)
UserInfoFirstNamePath=======?? (given_name)
UserInfoLastNamePath========?? (family_name)
DisplayName=================Office365
ExtraRoleNames==============?? (Administrator)

I'm unsure how to determine the JSON path to the UserInfo or how the ExtraRoleNames are used.

With the current settings, I am able to click on the Connect with Office365 option during login and it does show my Company Branded login page, but goes to a Server Error in '/' Application page showing a Runtime Error default page.

Anyone have any experience in this? Or if someone has successfully used the SAML option with Azure AD, those detailed instructions would also be helpful.

Edited by user Tuesday, February 13, 2018 8:54:05 PM(UTC)  | Reason: Not specified

I'm trying to use the SAML option, but it appears to be broken right now. Is there any significant difference in functionality using OAUTH2?

Hi Joey,

Do you have a support ticket with our team yet? We're actively trying to solve problems with the SAML before the release of 6.6.

Hi Mike,

is there also somewhere a guide how to configure SAML ADFS? i would like to try this with our new ADFS server.

Georg

Trying to setup Oauth with Office 365, but getting error with reply URL. Anyone know what this should be?

Hi,

I believe that is related to SAML?

Thanks,

Now getting a new error:

Error processing external login return: Could not load file or assembly 'System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxx' or one of its dependencies.

Is this because the server its running on is Linux?

A little silly that there is no official documentation for this , but here are the correct OAuth2 (OIDC) settings for Azure AD/Office 365:



You must set Reply Url in the Azure App Registration to "https://<ScreenConnect Domain>/__Authentication/<ScreenConnect OAuth Membership Provider ID>/Login". You can find the membership provider id by inspecting the request to Azure AD or looking in the web.config on the server under configuration->system.web->membership->providers->Your OAuth2 Provider->name. Personally, I just edited the web.config and set the "names" of my OAuth2 providers to match the Client ID of the App Registration in Azure AD for continuity.

You can create more than one OAuth2 provider, so I created a regular one for Helpdesk and and Admin one for administration. I used corresponding ScreenConnect roles and display names. In Azure AD under "Enterprise Applications" you can then assign users or groups to the apps, and force user assignment in the Enterprise Application properties.

Sol