Sign in with Azure loops

ramrajone

Testing on 1.17-RC3
When you click on sign in with Azure:

It goes back to the login page:

This happens with both users and Agents
is this related to the codebase or something I am doing wrong?

It lets me save the setting:

KevinTheJedi

You will need to make sure that the attributes do in fact match and that your email for the user matches the email on your providers end.

Cheers.

ntozier

Have you tried instead of mail, using:

userPrincipalName
firstName
lastName
userPrincipalName (or WindowsEmailAddress)

If it were simply AD then mail would be fine, but when i connect to EXO and pull user information I do not see an "mail" attribute anymore. Here's how I got to this to try:

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://ps.outlook.com/powershell/" -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session
Get-User -Identity "USERS NAME REDACTED" | format-list

NOTE: you will got a POPUP window to authenticate with your O365 account. If you do not have permissions to connect to EXO this way it will likely fail with a wall of red text with a buried permissions issue.

ntozier

follow up: the list of attributes is a little long... so be prepared to scroll a little.
You can remove a bunch of them if you want by adding attributes that you are looking for after format-list.

Like this:
Get-User -Identity "USERS NAME REDACTED" | format-list userPrincipalName,firstName,lastName,windowsEmailAddress

The result of this changed query would output something like:
UserPrincipalName : myEmailAddress@domain.tld
FirstName : Neil
LastName : Tozier
WindowsEmailAddress : myEmailAddress@domain.tld

ramrajone

ntozier

When using the Microsoft Edge browser, which is already signed into SSO, it just refreshes the page, but if you use the private mode, it does ask for the user/password, then refreshes back to the login page.

similar effects on Google Chrome and Firefox

After making changes and testing with another browser, I think it does the same thing, or maybe I am not entering the correct URL

update: correct URL
Resource Details Endpoint: *
User Details URL
https://graph.microsoft.com/v1.0/me

ramrajone

It's a long Monday, spent time with Microsoft, tried many different combination
Will continue tomorrow to see with fresh brain

At the moment Microsoft is pointing at application issues

KevinTheJedi

ramrajone As they always do 🤦‍♂️ They are literally no help at all...

msnowst

ramrajone did you resolve your issue? I'm seeing the same problems on 1.17.2 that started yesterday. My attributes and urls match your update. Azure is logging successful logins however both agents and clients are redirected in a loop.

KevinTheJedi

msnowst

Upgrade to either v1.17.4 or v1.18, install the latest build of the OAuth2 plugin, reset the instance config to default values, reconfigure by replacing the Authorization and Token Endpoints, and retest.

Cheers.

msnowst

I wanted to update, I continued to see issues after the upgrade to 1.18 and recreating the instance. However as I was in Azure getting the necessary details I found the client sectret had expired. Once I created a new secret and updated the instance all is working. Thank you for your assistance.