AddTemporarySigningCredential vs AddSigningCredential in IdentityServer4 : <p>According to the docs, IdentityServer uses an asymmetric key pair to sign and validate JWTs.
One could either use <code>AddTemporarySigningCredential()</code> in the configuration which creates a fresh RSA every startup or use <code>AddSigningCredential(..)</code> with an RSA key or a certificate.</p>

<p>The document mentions the Temporary version is useful for Development situations but it does not tell what is the disadvantage of this when used in a production environment. </p>

<p>I have a aspnetcore web api in which the clients are authenticated using the IdentityServer4. The system works fine at the moment with the temporarysigningcredential but I wonder whether there is any benefit in using the other variant.</p>

<p>Thanks,</p>
