Federation hangs when FQDN uses mixed casing.

[traetimmerman]

The deployment I'm working with is on-premises, and according to the Get-FQDN command in PowerShell, it looks like the FQDNs use mixed casing (e.g., server.Domain.Local). Token generation fails on the federation step, and I'm assuming this is because of the casing. Hitting the portal site using mixed casing redirects to site using all lower casing.

Just wanted to bring this to your attention in case there's a way to normalize casing in the logic in the federation step.

Thanks!