Skip to main content

System.Security.Cryptography.CryptographicException: The profile for the user is a temporary profile

Aaah, security errors, you have to love them. When deploying a new service on IIS, I got the following error:

Server Error in '/SampleService' Application.

clip_image002

The profile for the user is a temporary profile.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Security.Cryptography.CryptographicException: The profile for the user is a temporary profile.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[CryptographicException: The profile for the user is a temporary profile.]

   System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr) +33

   System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromFile(String fileName, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx) +0

   System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromFile(String fileName, Object password, X509KeyStorageFlags keyStorageFlags) +218

   System.Security.Cryptography.X509Certificates.X509Certificate..ctor(String fileName, String password, X509KeyStorageFlags keyStorageFlags) +65

   System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(String fileName, String password, X509KeyStorageFlags keyStorageFlags) +61

   CompanyX.Security.Service.Implementation.SecurityTokenServiceConfiguration..ctor() +143

   CompanyX.Security.Service.Implementation.WSTrustServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses) +25

   System.ServiceModel.HostingManager.CreateService(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) +1434

   System.ServiceModel.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity) +52

   System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) +598

[ServiceActivationException: The service '/SampleService/securityservice.svc' cannot be activated due to an exception during compilation.  The exception message is: The profile for the user is a temporary profile..]

   System.Runtime.AsyncResult.End(IAsyncResult result) +489276

   System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +178

   System.ServiceModel.Activation.ServiceHttpModule.EndProcessRequest(IAsyncResult ar) +350382

   System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +9692321

clip_image002[1]

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34249

I was able to trace the source of the error to the following line in my code:

var certificate = new X509Certificate2(certificate, password);

This statement fails to work in IIS because the application pool user / IIS user doesn’t have the necessary permissions.  This is because the certificate that I load will be temporarily stored in a certificate store, which by default is the user store. And here rises the problem as the application pool / IIS user does not have rights to that certificate store.

To solve this issue we have to add an extra parameter to the constructor where we specify we want to (temporarily) store the certificate in the machine store:

var certificate = new X509Certificate2(certificate, password, X509KeyStorageFlags.MachineKeySet);

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...