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

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more