Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 error when using AzureAD authentication #625

Closed
adamdriscoll opened this Issue Feb 13, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@adamdriscoll
Copy link
Member

adamdriscoll commented Feb 13, 2019

No description provided.

@adamdriscoll adamdriscoll added this to the 2.3.2 milestone Feb 13, 2019

@ArtisanByteCrafter

This comment has been minimized.

Copy link

ArtisanByteCrafter commented Feb 14, 2019

Yep, I'm seeing this behavior.

Removing the Azure AD authentication allows the dashboard to run.

Here's the authentication code I'm using:

# Authentication
$AzureADParams = @{
    ClientID = <CLIENT_ID>
    Instance = 'https://login.microsoftonline.com'
    Domain   = 'my.domain.com'
    TenantID = <MY_TENANT_ID>
}

$AuthenticationMethod = New-UDAuthenticationMethod @AzureADParams

$LoginPageParams = @{
    AuthenticationMethod     = $AuthenticationMethod
    LoadingText              = "MY_TEXT"
    LoginFormFontColor       = "#ffffff"
    LoginFormBackgroundColor = "#333333"
    LoginButtonFontColor     = "#FFFFFF"
    LoginButtonBackGroundColor = "#a80000"
    PageBackgroundColor      = "#222222"
    WelcomeText              = ""
    Logo                     = (New-UDImage -Url (Get-ImageBase64Uri -Path '.\assets\image.svg') -Width 450 -height 300)
}

$LoginPage = New-UDLoginPage @LoginPageParams
@TimCurwick

This comment has been minimized.

Copy link

TimCurwick commented Feb 14, 2019

Is the different broken behavior I described for on-prem AD authentication also being addressed under this issue or should I open a new issue?

@adamdriscoll

This comment has been minimized.

Copy link
Member Author

adamdriscoll commented Feb 15, 2019

@TimCurwick could you please open a separate issue? They might be related but I want to make sure not to miss either case.

adamdriscoll added a commit that referenced this issue Feb 15, 2019

@adamdriscoll

This comment has been minimized.

Copy link
Member Author

adamdriscoll commented Feb 15, 2019

I opened #640 to track the IIS issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.