starred/certbot-certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-07-28 08:45:22 +02:00
Code Issues Packages Projects Releases Wiki Activity

google: use Application Default Credentials where available (#9670)

Browse Source 
* google: use Application Default Credentials where available

* Updated custom role documentation
This commit is contained in:
Jawshua
2023-04-22 07:58:18 +10:00
committed by GitHub
parent 399b932a86
commit b0d0a83277
9 changed files with 360 additions and 211 deletions
Download Patch File Download Diff File Expand all files Collapse all files
certbot/CHANGELOG.md
+12 -1
View File
@@ -6,16 +6,27 @@ Certbot adheres to [Semantic Versioning](https://semver.org/).
### Added
* `--dns-google-project` optionally allows for specifying the project that the DNS zone(s) reside in,
which allows for Certbot usage in scenarios where the auth credentials reside in a different
project to the zone(s) that are being managed.
*
### Changed
* Lineage name validity is performed for new lineages. `--cert-name` may no longer contain
filepath separators (i.e. `/` or `\`, depending on the platform).
* `certbot-dns-google` now loads credentials using the standard [Application Default
Credentials](https://cloud.google.com/docs/authentication/application-default-credentials) strategy,
rather than explicitly requiring the Google Compute metadata server to be present if a service account
is not provided using `--dns-google-credentials`.
* `--dns-google-credentials` now supports additional types of file-based credential, such as
[External Account Credentials](https://google.aip.dev/auth/4117) created by Workload Identity
Federation. All file-based credentials implemented by the Google Auth library are supported.
*
### Fixed
*
* `certbot-dns-google` no longer requires deprecated `oauth2client` library.
More details about these changes can be found on our GitHub repo.