Skip to main content

WCF: Certificate EncodedValue

For a new application I’m building I have to use a certificate to connect to the WCF service. I didn’t want to pass the certificate through code instead I wanted to use the configuration model of WCF.

I found the following 2 options to specify the certificate. Either you put the certificate in your local certificate store and pass the certificate by using a certificatereference:

<identity>
<certificateReference findValue="DE74CFE7D20E8DC2B6E6E700E4D2A940CB08B268" storeLocation="LocalMachine" storeName="My" x509FindType="FindByThumbprint" />--><!--
</identity>

Another option is to embed the certificate into your application by specifying the base64 encoded value of the certificate:

<identity>
<certificate encodedValue="MIIGKjCCBRKgAwIBAgIKKwWMaS...TQymi87SNAM9H1dVaIfSysjc9BjhnhFm7HsINtj6S1g==" />
</identity>

But how do you get this encoded value?

If you are using the svcutil.exe to generate the client proxy, this value will be added for you. Otherwise you can get this value yourself:

  • Open the Certificate store
  • Right click on the certificate you want to embed and choose Export…
  • Choose to NOT export the private key
  • Choose the Base-64 encoded X.509 option

image

  • Choose a file name

Once the .CER file is exported, you can get the base64 encoded value by opening the .CER file in notepad and copying the string.

Labels:

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.
Read more

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...
Read more

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         ...
Read more