Skip to main content

Test a webservice using basic authentication with Fiddler

Last week I had to investigate an issue in an old webservice that was still using basic authentication(on a not enforced HTTPS connection Confused smile). With basic authentication you have to send a Base64 encoded version of your username/password combination to the server(that explains immediatelly why using basic authentication over a HTTP connection is never a good idea).

I had to the test the service but the only tool I had available on the server was Fiddler.

So let’s start by creating the Base64 encoded version of our message:

  • Open Fiddler
  • Go to Tools –> TextWizard…
  • Type your username password combination separated by a ‘:’, e.g. username:password
  • Choose ToBase64 from the Transform list
  • Copy the generated string

image

Next step is to create our request:

  • Go to the Composer tab
  • Type “Authorization: Basic’’after the User-Agent string and add the generated string to the end. The result should look like this:
Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

image

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