bug: LoadUserInfo with Resource is not handled by Blorc.OpenIdConnect

[kjbtech]

Describe the bug

When using the wasm sample, if I want to use the token in a protected resource (aka a web API),
I'm not redirected fully on my page after validated via LogTo login page.

For example, when I define:

  "IdentityServer": {
    "Authority": xx",
    "ClientId": "xx",
    "RedirectUri": "xx", // Remember to configure this in Logto
    "PostLogoutRedirectUri": "xx", // Remember to configure this in Logto
    "ResponseType": "code",
    "Scope": "openid profile",
    "LoadUserInfo": true,
    "Resource": "yy",
    "ExtraTokenParams": {
      "resource": "yy" // Ensure the key is lowercase
    }
  }

I get when I'm redirected to my website from LogTo:

If I remove the JSON node "ExtraTokenParams", no trouble!

Expected behavior

I'm redirecting to the LogTo login page.

How to reproduce?

Use the wasm sample provided in this repo and add:

    "Resource": "yy",
    "ExtraTokenParams": {
      "resource": "yy" // Ensure the key is lowercase
    }

Context

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

[gao-sun]

thanks for reporting and creating the pull, i'll take a look

[kjbtech]

We can close that, it was working!
The error was due becased I forgot to add the "/" at the end of the resource name.

[kjbtech]

Unfortunately, there is an error.

[kjbtech]

Hello,
Any update on this?

[kjbtech]

I implemented a .NET SDK to call the API management , but still in its infancy!

At this time, it simply helps to call the get user endpoint to avoid asking user info loading when authenticate.