Next, you need to ensure that your web.config file has forwardWindowsAuthToken set to true.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<!--
Configure your application settings in appsettings.json. Learn more at http://go.microsoft.com/fwlink/?LinkId=786380
-->
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath=".\net472\universaldashboard.server.exe" arguments="" stdoutLogEnabled="true" stdoutLogFile="\\?\%home%\LogFiles\stdout" forwardWindowsAuthToken="true" />
</system.webServer>
</configuration>
The last step is to configure your dashboard to use Windows authentication. Specify a new authentication method with the -Windows switch parameter and pass it to New-UDLoginPage. Include the -PassThru parameter to avoid having the login page shown. You should now be able to login to your UD site as the current user.
Claims-Based Authorization with Windows Authentication
You can use claims-based authorization with Windows Authentication by use the $UserPrincipal.HasClaims() method. There are several claims that will be provided by Windows to the Universal Dashboard authorization system. You can find a list here.
Here is an example of a dashboard that uses claims-based authorization and Windows authentication to verify that a user has particular group membership before showing a page.