This makecert script works perfectly to generate a token signing certificate usable with IdentityServer3. For some reason that I’m yet to uncover, the newer Powershell way on Windows 10 generates a cert that the signing piece in IdentityServer does not like. The powershell cert causes an exception like so:
IDX10614: AsymmetricSecurityKey.GetSignatureFormater( ‘http://www.w3.org/2001/04/xmldsig-more#rsa-sha256’ )
threw an exception.
Key: ‘System.IdentityModel.Tokens.X509AsymmetricSecurityKey’\nSignatureAlgorithm: ‘http://www.w3.org/2001/04/xmldsig-more#rsa-sha256’,
check to make sure the SignatureAlgorithm is supported.
Invalid provider type specified.
The original post follows:
I’ve been asked to post my makecert scripts for creating self-signed certificates (one for SSL and the other for signing). I use both of these scripts as .bat files. These scripts accept one …