Skip to content

Commit d2da06a

Browse files
Update hub request cert guide
1 parent 262124d commit d2da06a

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

docs/hub/guides/request-certificate.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Unique to *Certify Management Hub*, each managed certificate configuration and s
88

99

1010
# Configure a certificate authority
11-
A Certificate Authority is an entity which issues certificates (public or private). Before you can request a certificate you may need to configure a Certificate Authority ACME account on your target instance (where the certificate order will take place). To do so using the hub, go to *Settings* > *Certificate Authorities*, confirm your Target Instance selection and select *Add*.
11+
A Certificate Authority is an entity which issues certificates (public or private). Before you can request a certificate you may need to configure a Certificate Authority (ACME) account on your target instance (where the certificate order will take place). To do so using the hub, go to *Settings* > *Certificate Authorities*, confirm your Target Instance selection and select *Add*.
1212

1313
- [Let's Encrypt](https://letsencrypt.org) is the default CA. You can optionally enter an email address for contact about certificate renewal issues, then agree to the CAs terms and conditions and click OK. Note that omitting an email address will also prevent automated failure notifications provided by the certifytheweb.com API.
1414

@@ -20,12 +20,17 @@ Ordering a certificate from a CA requires specifying which identifiers (domains)
2020

2121
To add a new managed certificate:
2222
1. select *Certificates* > *New*
23-
- the *Target Instance* will default to the mangement hub server, but if you can optionally select a target Certify Certificate Manager instance (the instance must have already joined the hub).
23+
- the *Target Instance* will default to the management hub server, but you can optionally select a target *Certify Certificate Manager* instance (the instance must have already joined the hub).
2424
2. Provide a descriptive title for your certificate (for your own reference) and add the set of domains you want to include.
2525
3. On the *Authorization* tab, configure how to prove domain control by adding one or more challenge-response configurations. If your domain points to the same server as the *Target Instance* then that instance can provide HTTP domain validation responses. Otherwise, select dns-01 as the challenge type and configure an appropriate DNS validation method.
26+
4. You can then select "Test" to perform a basic check of your authorization configuration, then select Request Certificate to begin your certificate order with the CA.
2627

2728
:::info
2829

29-
Note: If you intend to create a test certificate against the Staging version of a CA, select *Certificate* > *Advanced* > *Certificate Authority*, select your CA and check *Use Staging Mode*.
30+
Note: If you want to create a test certificate using a CA’s Staging environment, select *Certificate > Advanced > Certificate Authority*, choose your CA, and check *Use Staging Mode*.
3031

31-
:::
32+
:::
33+
34+
Once your certificate request is working, you can decide how to use the certificate: either use it on the same server as the Management Hub, or export it for use elsewhere using a deployment task under Tasks.
35+
36+
You can also use the hub API from any other machine to pull the latest version of the certificate.

0 commit comments

Comments
 (0)