Fixed the solution for challenge11 for azure, closing
@@ -13,6 +13,10 @@ metadata:
aadpodidbinding: separate-workload-pod-id
spec:
template:
+ metadata:
+ name: wrongsecret3job
+ labels:
+ aadpodidbinding: separate-workload-pod-id
spec:
containers:
- name: az
@@ -25,4 +29,4 @@ spec:
```
- Apply the job with `kubectl apply -f job.yaml`
-You can now exec into the pod, and execute something like `az login --identity --allow-no-subscriptions && az keyvault secret show --name wrongsecret-3 --vault-name wrongsecrets-vault-00000`. Since the job can access the same vault as the secret challenge pod, it has access to its secrets.
+You can now exec into the pod, and execute something like `az login --identity --allow-no-subscriptions && az keyvault secret show --name wrongsecret-3 --vault-name wrongsecrets-vault-00000` . Note that you can find the actual value of `wrongsecrets-vault-00000` in the terraform state. Since the job can access the same vault as the secret challenge pod, it has access to its secrets.
