Closed haukehem closed 2 days ago
I have gathered further information on this exception's origin. It is thrown during the /connect/token
-call when, while starting the authentication flow via the /connect/authorize
-redirect, the IdentityServerApi
-scope is requested. This scope is required because I added custom actions to my IdentityServer. These actions require the [Authorize(LocalApi.PolicyName)]
-annotation.
Can you please provide us with the column values of the record in the Keys table? (Except for data perhaps if that's too long/sensitive)
Hi! Sorry for the small delay - sure, the values in my Key table are:
I only have this one row in the Key table.
We're still investiging this. Can you please share the configuration of your ApiResource?
@haukehem Is your problem solved? If so I would like to close this issue.
Closing for now but feel free to reopen if you feel the need to add a comment.
Which version of Duende IdentityServer 7.0.5
Which version of .NET 8.0.3
Description/Repro I configured my IdentityServer middleware to use persistent database stores for configuration and operational data as well as automatic key management with the database store implementation:
In my database, there is a Authorization Code + PKCE flow client and also one entry in the Keys table. In the client db entry, the
AllowedIdentityTokenSigningAlgorithms
is set to null as expected. When trying to obtain a token via Postman, I successfully get redirected back from the/connect/authorize
call, but when calling/connect/token
afterwards, the IdentityServer throws anInvalidOperationException: No signing credential for algorithm (True) registered.
Log output/exception with stacktrace