Nyami’s Blog

Something interesting for sure…

Creating a Self-Signed Certificate for Identity Provider

| Comments

I’d recently had to create a self-signed certificate for use in IdentityProvider4 and was coming up against problems when using the default options with New-SelfSignedCertificate PS module.

Identity Server was throwing “CryptographicException: Invalid provider type specified” and I had ensured the user account had access so it should have been all good. After a little bit of digging it turned out the private keys were not accessible from .NET. David Christiansen’s blog post helped me track down the issue but with a little more research I ended up with the following PowerShell to create a working certificate avoiding additional steps I didnt understand ;).

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
$idSrvCertificate = New-SelfSignedCertificate `
    -Subject "CN=MyIdentityProviderCert" `
    -FriendlyName "Identity Server Token Signing" `
    -CertStoreLocation "cert:LocalMachine\My" `
    -KeyAlgorithm RSA `
    -KeySpec Signature `
    -KeyLength 2048 `
    -KeyUsage DigitalSignature, KeyEncipherment, DataEncipherment, CertSign `
    -NotBefore (Get-Date) `
    -NotAfter (Get-Date).AddYears(5);

$username = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name;

$keyname = (((Get-ChildItem cert:\LocalMachine\my | Where-Object {$_.thumbprint -like $idSrvCertificate.ThumbPrint}).PrivateKey).CspKeyContainerInfo).UniqueKeyContainerName;

$keypath = $env:ProgramData + "\Microsoft\Crypto\RSA\MachineKeys\";
$fullpath = $keypath + $keyname;
icacls $fullpath /grant $username`:RX;

In addition to creating the certificate it will also ensure the current user has read access to the private keys avoiding the need to run VS elevated when developing, this last part could obviously be extracted and reused for your application pool if running Identity Server in IIS.

Comments