How do I fix an OIDC thumbprint mismatch? #750
-
We have configured GitHub Actions to be able to assume the deployment role in our Reference Architecture A GitHub Actions run failed today with this error:
Some Googling turned up this blog post from GitHub: it seems that at some point recently they added a second certificate chain with different thumbprint to the GitHub Actions service. How do we fix this? (this post was modified from it's original to pose it as a question with an answer in a comment so that the answer could be marked as accepted) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Credit to @adamlundrigan (I extracted this from his initial post): I checked our this presumably only extracts one of the thumbprints (the one for the certificate Our workaround is to hard-code the list of thumbprints:
We should fix the extraction to pull both certificates. Thanks, @adamlundrigan ! |
Beta Was this translation helpful? Give feedback.
Credit to @adamlundrigan (I extracted this from his initial post):
I checked our
account-baseline-app
module forshared
and we're not explicitly setting a list of thumbprints viagithub_actions_openid_connect_provider_thumbprint_list
, which means the Terraform is falling back to extracting the certificate thumbprint fromhttps://token.actions.githubusercontent.com
:https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/2b35fe7ab89482e57a5746f1b14e31974dfb8f22/modules/landingzone/account-baseline-app/main.tf#L552-L558
this presumably only extracts one of the thumbprints (the one for the certificate
https://token.actions.githubusercontent.com
used), which then causes our GitHub …