Problem with openid configuration Content Delivery API (lack a file .well-known/jwks)

Questions
, ,
1

During migration from v13 to v16 through all versions I noticed that I can’t login to the system because file .well-known/jwks is not available and returns 404 during login. It is working fine with v13.9.2.
Any reason why this file is not exists for .well-known/openid-configuration?

What you can do to reproduce it:

  1. Prepare configuration for Content Delivery API:
    "DeliveryApi": { "Enabled": true, "PublicAccess": true, "MemberAuthorization": { "AuthorizationCodeFlow": { "Enabled": true, "LoginRedirectUrls": [ "https://localhost:4200/auth/callback" ], "LogoutRedirectUrls": [ "http://localhost:4200/" ] } }
  2. Go to file: {baseUrl}/.well-known/openid-configuration/
  3. Try open {baseUrl}/.well-known/jwks
  4. This file is not found.

.well-known/openid-configuration file:

The image shows a snippet of JSON code, likely representing a configuration or metadata document related to security or authentication, with various keys such as "issuer," "authorization_endpoint," and "grant_types_supported," all set to specific URL values or arrays of strings. (Captioned by AI)
The image shows a snippet of JSON code, likely representing a configuration or metadata document related to security or authentication, with various keys such as "issuer," "authorization_endpoint," and "grant_types_supported," all set to specific URL values or arrays of strings. (Captioned by AI)800×705 17.5 KB

Then I can’t to login using oicd package on client side (angular) to go to authorized content.