logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
pchrist18  
#1 Posted : Tuesday, February 13, 2018 8:49:11 PM(UTC)
pchrist18


Rank: Guest

Joined: 2/13/2018(UTC)
Posts: 2
United States

Was thanked: 1 time(s) in 1 post(s)
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

pchrist18  
#2 Posted : Thursday, February 15, 2018 2:19:23 PM(UTC)
pchrist18


Rank: Guest

Joined: 2/13/2018(UTC)
Posts: 2
United States

Was thanked: 1 time(s) in 1 post(s)
I was able to get some help from Support on this if anyone is interested in implementing Azure AD login.

ClientID====================Application ID from Azure
ClientSecret================Key Generated from App Registration
AccessCodeServiceUri========Auth 2.0 Authorization Endpoint
AccessTokenServiceUri=======OAuth 2.0 Token Endpoint
UserInfoServiceUri==========https://graph.microsoft.com/v1.0/me
ResourceID==================https://graph.microsoft.com
UserInfoIDPath==============id
UserInfoEmailPath===========mail
UserInfoFirstNamePath=======givenName
UserInfoLastNamePath========surname
DisplayName=================Office365
ExtraRoleNames==============Security Group that matches Control Role Name

Currently the ExtraRoleNames mapping isn't working correctly and it will only apply 1 role that is defined in this field.

Edited by user Thursday, February 15, 2018 4:19:09 PM(UTC)  | Reason: Not specified

thanks 1 user thanked pchrist18 for this useful post.
Mike on 2/15/2018(UTC)
joey52685  
#3 Posted : Saturday, February 17, 2018 12:33:35 PM(UTC)
joey52685


Rank: Guest

Joined: 2/16/2018(UTC)
Posts: 2
United States

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?
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.