Skip to main content

WSFederation broken after upgrade to .NET 8

This week a colleague contacted me with an issue he encountered after upgrading to .NET 8.0. On the project involved we were using the WsFederation middleware to authenticate and interact with ADFS. However after upgrading to .NET 8 and the 8.x version of the Microsoft.AspNetCore.Authentication.WsFederation middleware the trouble began.

Using this version resulted in a change in behavior as suddenly the middleware starts to expect a SAML 2.0 token instead of a SAML 1.1 token that is now issued by our ADFS server:

XmlReadException: IDX30011: Unable to read XML. Expecting XmlReader to be at ns.element: 'urn:oasis:names:tc:SAML:2.0:assertion.Assertion', found: 'urn:oasis:names:tc:SAML:1.0:assertion.Assertion'.

Although I found a post online that it would be technically possible to let ADFS return a SAML 2.0 token through WSTrust, this doesn’t fit in the passive federation scenario we had, so time to look at some alternative solutions.

Attempt 1 – Reverting to an older package version

We first tried to rollback to an older version of the WSFederation middleware but that caused an issue in a transitive dependency. In the project we were using both Microsoft.Data;SqlClient and Microsoft.AspNetCore.Authentication.WsFederation. Both packages reference the Microsoft.IdentityModel.Tokens package as a shared dependency. However as the Microsoft.Data.SqlClient expects at least version 6.35.0 of the package and Microsoft.AspNetCore.Authentication.WsFederation expects at least version 6.10.0, version 6.35.0 of the Microsoft.IdentityModel.Tokens package is used.

Using this version resulted in a MissingMethodException as the Microsoft.IdentityModel.Tokens.InternalValidators.ValidateLifetimeAndIssuerAfterSignatureNotValidatedSaml method no longer exists in this package.

So no luck, we had to try something else...

Attempt 2 - Adding the Microsoft.IdentityModel.Tokens.Saml package

Further investigation brought me to the following issue on GitHub: Authentication.WsFederation breaks with on-premise AD FS use · Issue #52099 · dotnet/aspnetcore

Their was mentioned that explicitly adding the following NuGet package had fixed the issue:

NuGet Gallery | Microsoft.IdentityModel.Tokens.Saml 8.10.0

We followed this advice and indeed that fixed the problem.

On to the next one…

More information

NuGet Gallery | Microsoft.AspNetCore.Authentication.WsFederation 8.0.16

Obtaining a SAML 2.0 assertion from AD FS by using WS-Trust and Integrated Windows Authentication

Authentication.WsFederation breaks with on-premise AD FS use · Issue #52099 · dotnet/aspnetcore

NuGet Gallery | Microsoft.IdentityModel.Tokens.Saml 8.10.0

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more