Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SSL certificate error #1939

Merged
merged 5 commits into from
Jun 21, 2024
Merged

Conversation

jemrobinson
Copy link
Member

@jemrobinson jemrobinson commented Jun 17, 2024

✅ Checklist

  • You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
  • You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
  • Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

🚦 Depends on

n/a

⤴️ Summary

Workaround for an issue where Let's Encrypt refused to provide certificates for uppercase FQDNs

🌂 Related issues

Closes #1938

🔬 Tests

Tested inside function but not more widely. Waiting for a test report from original bug report provider.
Now confirmed that this fixes #1938.

@jemrobinson jemrobinson requested review from a team June 17, 2024 13:13
JimMadge
JimMadge previously approved these changes Jun 18, 2024
@craddm
Copy link
Contributor

craddm commented Jun 19, 2024

Testing was held up by #1947

@jemrobinson
Copy link
Member Author

@craddm @JimMadge : should we merge this and fix #1947 in another PR to latest?

@craddm
Copy link
Contributor

craddm commented Jun 20, 2024

I'm still running through a test deployment. Hit this error now:

Submit-ChallengeValidation: Authorization invalid for guacamole-sre-t2caps.blue.develop.turingsafehaven.ac.uk: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.guacamole-sre-t2caps.blue.develop.turingsafehaven.ac.uk - check that a DNS record exists for this domain
2024-06-20 21:49:53 [SUCCESS]: [✔] Certificate creation succeeded                               
2024-06-20 21:49:53 [   INFO]: Importing signed certificate into Key Vault 'kv-blue-sre-t2caps'...
2024-06-20 21:49:53 [FAILURE]: [x] Certificate import failed!
Import-AzKeyVaultCertificate: /workspaces/data-safe-haven/deployment/secure_research_environment/setup/Update_SRE_SSL_Certificate.ps1:225:125
Line |
 225 |  … lt.name -Name $certificateName -FilePath $certificateFilePath -ErrorA …
     |                                             ~~~~~~~~~~~~~~~~~~~~
     | Cannot bind argument to parameter 'FilePath' because it is an empty string.

@jemrobinson
Copy link
Member Author

This is actually very adjacent to the original error! Can you post a bit more context?

@JimMadge
Copy link
Member

Looks like maybe there is another bug to fix here?

@jemrobinson
Copy link
Member Author

Looks like the blue.develop.turingsafehaven.ac.uk DNS zone is missing. Can you re-run the SHM deploy scripts @craddm ?

Screenshot 2024-06-21 at 09 31 15

@jemrobinson jemrobinson changed the base branch from latest to release-v4.2.2 June 21, 2024 10:35
@jemrobinson
Copy link
Member Author

I'm merging this into release-v4.2.2 as the original problem is fixed. I'll open a new release-candidate PR from that branch.

@jemrobinson jemrobinson merged commit 479855b into release-v4.2.2 Jun 21, 2024
11 checks passed
@jemrobinson jemrobinson deleted the 1938-ssl-certificate-error branch June 21, 2024 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants