openiddict-core: After deployment to IIS Server: A signing key must be provided
Dear community,
Since a newer version of openiddict I am having an issue with deployment to my IIS host. It seems that the access token cannot be signed anymore. I got the following error: A signing key must be provided
I also tried to install a self cert 509 certificate using the plural sight cert tool and installed it added it to the startup config using AddSigningCertificate() (see below):
// Register the OpenIddict services, including the default Entity Framework stores.
services.AddOpenIddict<ApplicationUser, ApplicationRole, ApplicationDbContext>()
.AddTokenManager<CustomOpenIddictTokenManager>()
.AddUserManager<CustomOpenIddictUserManager>()
.EnableTokenEndpoint("/connect/token")
.AllowPasswordFlow()
.AllowRefreshTokenFlow()
.AddSigningCertificate("64CDD1397EF7E90869E4F50741EF55FDBE583781", StoreName.My, StoreLocation.LocalMachine) //Self-Signed-Cert using https://www.pluralsight.com/blog/software-development/selfcert-create-a-self-signed-certificate-interactively-gui-or-programmatically-in-net
// During development, you can disable the HTTPS requirement.
//.DisableHttpsRequirement()
.UseJsonWebTokens();
Using my own 509 certificate I got the error:
opencsp failed with error code 2148073494
Any help/hints appreciated. Thanks, Joël
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 1
- Comments: 22 (11 by maintainers)
FYI, I tested on IIS 7.5 (Windows 7), with ApplicationPoolIdentity and “load user profile” disabled.