Doesnt work on Local IIS, found bug... about openiddict-core HOT 3 CLOSED

The reason that the site never loaded, was because OpenIddict, seems to create a [GUID].key file in the wwwroot of the published site. Because my IISPOOL/XXX user doesnt have write permission to the wwwroot folder (which i dont think it should), this process failed.

When you don't explicitly register a signing key, one is automatically created and persisted for you on the disk (in the AppData folder or in the current directory if the user profile is not available).

Last week, I pushed a commit to replace the last fallback value to use the TEMP directory instead of the current directory, so the "bug" you're seeing should disappear when updating your packages: aspnet-contrib/AspNet.Security.OpenIdConnect.Server@f22d2ea

Have i setup something wrong? Should i have stated something in my startup.cs file to write this file to another place??

Using a X509 certificate stored in the machine store is recommended for production environments:

app.UseOpenIddict(builder => {
    builder.Options.SigningCredentials.AddCertificate("thumbprint");
});

You can also load it from a file:

app.UseOpenIddict(builder => {
    builder.Options.SigningCredentials.AddCertificate(new X509Certificate2("path", "password"));
});

from openiddict-core.

@PinpointTownes Thanks for this, this works perfectly

from openiddict-core.

Nice! 👏

from openiddict-core.