Skip to main content

Identity Server 4 - Angular–Chrome’s samesite cookie changes

Today I got into trouble when I tried to run an Ionic(Angular) application we had build. After being redirect to IdentityServer and returned to my application after  a successful login, a few seconds later I got the message that my session was expired and that I had to login again(and again, and again, …).

Inside our application we are using the great angular-oauth2-oidc library. One of it’s nice features is that it keeps our identity and access tokens up-to-date thanks to a built-in silent refresh mechanism. This mechanism uses a hidden iframe to call IdentityServer to renew our tokens.

Remark: we need this hidden iframe hack as we are still using an Implicit Flow. The plan is to switch to Code Flow which allows us to use refresh tokens.

Inside the developer console I see the following warnings:

A cookie associated with a cross-site resource at https://ids.development/ was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

It is the refresh that fails inside the iframe. The angular-oauth2-oidc library returned the following messages:

angular-oauth2-oidc.js:757 sessionCheckEventListener

angular-oauth2-oidc.js:757 sessionCheckEventListener wrong origin https://localhost expected https://ids.development

angular-oauth2-oidc.js:757 got info from session check inframe MessageEvent {isTrusted: true, data: "#error=login_required&state=pBN472WnAzQQ_IGcGSqpyq3-5mPtT-si9XSclJPpLirjm", origin: "https://localhost", lastEventId: "", source: Window, …}

angular-oauth2-oidc.js:757 parsed url {error: "login_required", state: "pBN472WnAzQQ_IGcGSqpyq3-5mPtT-si9XSclJPpLirjm"}

angular-oauth2-oidc.js:757 error trying to login

angular-oauth2-oidc.js:757 silent refresh did not work after session changed

angular-oauth2-oidc.js:757 silent refresh failed after session changed

To fix it, we have to do a change in IdentityServer and configure a different cookie policy:

More information: https://www.thinktecture.com/en/identity/samesite/prepare-your-identityserver/

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

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