Asp.net core 8.0.17 breaks redirectURI

[mrcandido]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

We have a .net 8 Blazor application running behind a reverse proxy. The application uses Okta for authentication. The application was working fine until the asp.net core hosting bundle 8.0.17 was pushed to the servers.

After that, the application started sending the server name to Okta in the redirect URI parameter instead of the external URL.

Reverting to asp.net core hosting bundle 8.0.16 fixed the issue.

Expected Behavior

The external URL should be passed to Okta as the redirect URI, not the internal server name.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0

Anything else?

No response

[BrennanConroy]

dotnet/core#9930

[yongkeecho]

The issue is resolved by downgrading the Microsoft.AspNetCore.Authentication.OpenIdConnect package from 9.0.6 to 9.0.5.

[Viktor-36]

dotnet/core#9930

I had same issue in version 9.0.6. You should check #61622 ... There is some discussion about it. It was released in 8.0.17 as #61623

It looks like you have to set properties KnownNetworks and KnownProxies in ForwardedHeadersOptions now. You can also use quick workaround below (it worked for me), but it will be better to set those properties to be safe.

More info dotnet/core#9930 as @BrennanConroy mentioned above.

builder.Services.Configure<ForwardedHeadersOptions>(options =>
{
    options.ForwardedHeaders = ForwardedHeaders.XForwardedProto;
    options.KnownNetworks.Clear();
    options.KnownProxies.Clear();
})

[mrcandido]

dotnet/core#9930

I had same issue in version 9.0.6. You should check #61622 ... There is some discussion about it. It was released in 8.0.17 as #61623

It looks like you have to set properties KnownNetworks and KnownProxies in ForwardedHeadersOptions now. You can also use quick workaround below (it worked for me), but it will be better to set those properties to be safe.

More info dotnet/core#9930 as @BrennanConroy mentioned above.

builder.Services.Configure(options =>
{
options.ForwardedHeaders = ForwardedHeaders.XForwardedProto;
options.KnownNetworks.Clear();
options.KnownProxies.Clear();
})

Thanks for sharing. We will try this workaround as a short-term solution and work on the new configuration for the long-term