Skip to content

Commit 9944f2f

Browse files
author
Keyfactor
committed
Update generated docs
1 parent ea70dfb commit 9944f2f

2 files changed

Lines changed: 2 additions & 22 deletions

File tree

README.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -315,7 +315,7 @@ The RFC 2136 provider enables ACME DNS-01 challenges with on-premise DNS servers
315315
* **EabKid** - External Account Binding Key ID (optional)
316316
* **EabHmacKey** - External Account Binding HMAC key (optional)
317317
* **SignerEncryptionPhrase** - Used to encrypt singer information when account is saved to disk (optional)
318-
* **DnsProvider** - DNS Provider to use for ACME DNS-01 challenges (options: Google, Cloudflare, AwsRoute53, Azure, Ns1, Rfc2136, WindowsDns)
318+
* **DnsProvider** - DNS Provider to use for ACME DNS-01 challenges (options: Google, Cloudflare, AwsRoute53, Azure, Ns1, Rfc2136)
319319
* **Google_ServiceAccountKeyPath** - Google Cloud DNS: Path to service account JSON key file only if using Google DNS (Optional)
320320
* **Google_ProjectId** - Google Cloud DNS: Project ID only if using Google DNS (Optional)
321321
* **Cloudflare_ApiToken** - Cloudflare DNS: API Token only if using Cloudflare DNS (Optional)
@@ -332,10 +332,6 @@ The RFC 2136 provider enables ACME DNS-01 challenges with on-premise DNS servers
332332
* **Rfc2136_TsigKeyName** - RFC 2136 DNS: TSIG key name for authentication (Optional)
333333
* **Rfc2136_TsigKey** - RFC 2136 DNS: TSIG key (base64 encoded) for authentication (Optional)
334334
* **Rfc2136_TsigAlgorithm** - RFC 2136 DNS: TSIG algorithm (default hmac-sha256) (Optional)
335-
* **WindowsDns_Server** - Windows DNS: Server hostname (leave empty for local server) (Optional)
336-
* **WindowsDns_Zone** - Windows DNS: Zone name (e.g., test.local) (Optional)
337-
* **WindowsDns_Username** - Windows DNS: Username for remote server (domain\user format) (Optional)
338-
* **WindowsDns_Password** - Windows DNS: Password for remote server (Optional)
339335
* **DnsVerificationServer** - DNS server to use for verifying TXT record propagation. For private/local DNS zones, set this to your authoritative DNS server IP (e.g., 10.3.10.37). Leave empty to use public DNS servers (Google, Cloudflare, etc.).
340336
341337
2. Define [Certificate Profiles](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCP-Gateway.htm) and [Certificate Templates](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCA-Gateway.htm) for the Certificate Authority as required. One Certificate Profile must be defined per Certificate Template. It's recommended that each Certificate Profile be named after the Product ID. The Acme plugin supports the following product IDs:

integration-manifest.json

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
},
3636
{
3737
"name": "DnsProvider",
38-
"description": "DNS Provider to use for ACME DNS-01 challenges (options: Google, Cloudflare, AwsRoute53, Azure, Ns1, Rfc2136, WindowsDns)"
38+
"description": "DNS Provider to use for ACME DNS-01 challenges (options: Google, Cloudflare, AwsRoute53, Azure, Ns1, Rfc2136)"
3939
},
4040
{
4141
"name": "Google_ServiceAccountKeyPath",
@@ -101,22 +101,6 @@
101101
"name": "Rfc2136_TsigAlgorithm",
102102
"description": "RFC 2136 DNS: TSIG algorithm (default hmac-sha256) (Optional)"
103103
},
104-
{
105-
"name": "WindowsDns_Server",
106-
"description": "Windows DNS: Server hostname (leave empty for local server) (Optional)"
107-
},
108-
{
109-
"name": "WindowsDns_Zone",
110-
"description": "Windows DNS: Zone name (e.g., test.local) (Optional)"
111-
},
112-
{
113-
"name": "WindowsDns_Username",
114-
"description": "Windows DNS: Username for remote server (domain\\user format) (Optional)"
115-
},
116-
{
117-
"name": "WindowsDns_Password",
118-
"description": "Windows DNS: Password for remote server (Optional)"
119-
},
120104
{
121105
"name": "DnsVerificationServer",
122106
"description": "DNS server to use for verifying TXT record propagation. For private/local DNS zones, set this to your authoritative DNS server IP (e.g., 10.3.10.37). Leave empty to use public DNS servers (Google, Cloudflare, etc.)."

0 commit comments

Comments
 (0)