Identityserver4: [Question] Startup.cs - throw new Exception("need to configure key material");

[LaurentFromParis]

Hi,

This is not a bug, just a question.
When I tryed to execute dotnet MyIdServer.dll /seed
I got : throw new Exception("need to configure key material");

I did this :
`

if DEBUG

            var certPath = Path.Combine(Directory.GetCurrentDirectory(), "Cert", "MyIdServerLocalhost.pfx"); //IISExpressCertificate
            X509Certificate2 cert = new X509Certificate2(certPath, "MyLocalhostCertPassword");

else

                var certPath = Path.Combine(Directory.GetCurrentDirectory(), "Cert", "MyIdServer.pfx");
                X509Certificate2 cert = new X509Certificate2(certPath,"MyProductionCertPassword");

endif

builder.AddSigningCredential(cert);
`

My question is :
This means when you seed the database for production, you cannot use it in localhost test mode because some encryption is different ?

If yes, do I have to seed a first database for localhost with a first connectionstring and a second one for production ?

Thanks

[brockallen]

The docs have many of your answers:
http://docs.identityserver.io/en/release/quickstarts/0_overview.html
http://docs.identityserver.io/en/release/topics/crypto.html

[leastprivilege]

Also - learn about the hosting environment concept in ASP.NET Core - this is orthogonal to DEBUG.

[brockallen]

Closing. If you still have issues, feel free to reopen.

[Alex2357]

The docs have many of your answers:
http://docs.identityserver.io/en/release/quickstarts/0_overview.html
http://docs.identityserver.io/en/release/topics/crypto.html

The links are broken. Could you update them?

[jmb1304]

Here are the updated links:

http://docs.identityserver.io/en/latest/quickstarts/0_overview.html

http://docs.identityserver.io/en/latest/topics/crypto.html

[Alex2357]

Here are the updated links:

http://docs.identityserver.io/en/latest/quickstarts/0_overview.html

http://docs.identityserver.io/en/latest/topics/crypto.html

Thanks for the update

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.