Describe the bug

I have a Blazor Server project, where I have added Logto as an Identity Provider. I have created a Traditional Web App in Logto and provided all information for the AddLogotAuthentication call. I tested it and everything worked fine. Than I added a API Resource to Logto and added the ID of it to options.Resource. But after adding that and starting the App, I never get Authenticated again. Always when clicking login, and logging in on logto, I get redirected to my page and it still says Login. Only when I remove the Resource again, my login works fine.
I currently tried several Resource IDs:

• https://localhost:port/
• http://localhost:port/
• https://api.domain.de/

I can also reproduce that behaviour in the Blazor Sample App.
If you need more information, I am happy to share ^^

Expected behavior

I still get Authenticated correctly on my Application, and can retrieve my Access Token for my WebAPI.

How to reproduce?

Download this repo, open the Blazor Server Project, add the appsettings, add a Traditional Web App to logto and fill the required information in the appsettings. Add a API Resource to logto and add the resource to the appsettings. Try to login.

Context

• Logto Cloud
• Self-hosted, Logto version = 1.20.0
  • Container (Docker image)
  • Raw Node.js

Screenshots

Before Sign-in:

After Sign-In: