Heya,
I think I know what’s going on here. IIRC, this is an issue with how the configuration system is handling arrays. What’s happening here is that the array is being appended to, instead of completely replaced. In the interim you’ll need to update this in HordeHTTPAuthHandler.cs
async Task<AuthState> GetAuthStateInternalAsync(bool interactive, CancellationToken cancellationToken) { // ... //string? localRedirectUrl = authConfig.LocalRedirectUrls?.FirstOrDefault(); string? localRedirectUrl = authConfig.LocalRedirectUrls?.:LastOrDefault(); // ... }I was able to validate this on my own end by attaching a debugger to the server, and stepping through the GetAuthConfig endpoint. I vaguely remember an internal ticket about this; I’ll see if I can pull it up.
Edit: Microsoft github thread about this
Kind regards,
Julian