bug: OIDC server returns "resource indicator must be an absolute URI" error

[charIeszhao]

Describe the bug

If we create the API resource identifier as a valid simple domain without pathname, such as https://logto.io, the OIDC server will return an unexpected "resource indicator must be an absolute URI" error, even though the identifier is a valid URL.

Currently, the workaround is to use an identifier URL followed by either a trailing slash / or a pathname /foo instead.

Expected behavior

Resource identifiers like https://logto.io should also work.

How to reproduce?

• Create an API resource in Logto Console, and input a simple domain http://example.com as the indicator.
• Use this api resource in a client app, say "react sample", and pass it into Logto configs as resources: ['https://example.com']
• Sign in, and the OIDC auth server will report an error in its redirect URL: resource indicator must be an absolute URI

Context

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

Screenshots

[charIeszhao]

The root cause was found in our underlying service library. A pull request has been filed and will update it on our end as soon as the patch is available.