Ok, so i’m runing the latest UA 1.5.0 night build. I’ve setup UA to run as a service under a service account. Did the setspn thing accordingly to the doc here: Security - PowerShell Universal
Created a new Dashboard via UA. Thing is: I can single sign on from the host, even from other computers on the lan, but i can’t sign on in the dashboard. I tried display the $User variable in the dashboard. I does not show. If I select authentication on the dashboard (via UA) the I can, again single sign on on UA (no problem here) but when i go to the Universal Dashboard i just created, it pops up the Login page. In the login page i cannot sign in with any user.
Made modification to web.config : forwardWindowsAuthToken=“true”
Made modification to app setting:
“Authentication” : {
“Windows”: {
“Enabled”: “true”
},
also in app setting i modified this:
“Kestrel”: {
“Endpoints”: {
“HTTP”: {
“Url”: “http://*:80”
}
}
Any suggestions why Windows Auth might not work on the Dashboard ?
Any workarrounds ?
Actually, i don’t even need auth, i just need the name of the user logged in on the computer that is using the Universal Dashboard.
Thanks.
Hello again, tried the latest night build ( 330216916 Tue, 27 Oct 2020 00:33:25 GMT) still same issue.
Here is a demo (with dashboard authentication on):
and here is a second demo without dashboard authentication:
@PowerCode-K talked with Adam regarding this issue. with the last nightly build 1.5.0 the bug was resolved. it is working fine for me now. you should give it a try. if you still have problems, I might be able to guide you trough as i learned a lot from my experience setting UA and UD up.
@PowerCode-K 'm still having issues with Windows Authentication, specifically with IIS. IIS windows authentication appears to work ok, however, it asks me for credentials a second time.
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_w3wp.exe_a8f7660cd44ba0ac261a6a57ef9c551ef2e3fb_98baeb8b_1b6a5bfd
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Universal.Server_294bad55d99f7254dc593ae225c9d0507f73dbd5_b4cd54dd_0e655e95
@crypticsh I know on the IIS and service account installation you have to force http1. Http 2 won’t pass windows authentication. When using chrome i had to change some setting to correctly pass authentication.
Thanks @PowerCode-K , do you remember what you did to force http1? I tried a few things from disabling http2 in the windows registry to using the --disable-http2 flag launching chrome with no luck (I rebooted etc. in between most testing). Are you running in IIS or as a service?
I guess the only difference between my scenario and the OP, is they are running as a service and I’m running it in IIS. I may end up trying that to see if that works.
Adam, if there is anything else you need from me or what me to try, let me know.