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.

Sign up for GitHub

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

Jump to bottom

Fix links to ACME main page #256

Merged
merged 1 commit into from
Jul 24, 2023
Merged

Fix links to ACME main page #256

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions certificate-manager/how-it-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ Some of the more popular workflows provisioners enable include:
Let's Encrypt. It can be used to automatically get a certificate for a domain
name or IP address. A rich client ecosystem and built-in support in many tools
makes ACME easy to integrate. See the
[ACME documentation](./acme.mdx) to learn more.
[ACME documentation](./acme/README.mdx) to learn more.
- **Single Sign-on**: The `OIDC` provisioner uses
[OAuth](https://datatracker.ietf.org/doc/html/rfc6749) and
[OpenID Connect (OIDC)](https://openid.net/specs/openid-connect-core-1_0.html)
Expand Down Expand Up @@ -574,7 +574,7 @@ ACME works almost anywhere and is especially useful for issuing certificates to
web servers for use with TLS. To issue certificates for internal names that
aren't in public DNS the ACME server does need access to local DNS. It's common
to use a linked CA or a network-local RA. Reference the
[Certificate Manager docs](./acme.mdx) for more details.
[Certificate Manager docs](./acme/README.mdx) for more details.

## Next steps

Expand Down
2 changes: 1 addition & 1 deletion step-ca/acme-basics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ ACME is a modern, standardized protocol for automatic validation and issuance of
## Requirements

- **Open source -** This tutorial assumes you have initialized and started up a `step-ca` server (see [Getting Started](./getting-started.mdx)).
- **[Smallstep Certificate Manager](https://smallstep.com/certificate-manager) -** follow the instructions provided in the Certificate Manager [ACME documentation](../certificate-manager/acme.mdx).
- **[Smallstep Certificate Manager](https://smallstep.com/certificate-manager) -** follow the instructions provided in the Certificate Manager [ACME documentation](../certificate-manager/acme/README.mdx).

## Overview

Expand Down
2 changes: 1 addition & 1 deletion tutorials/acme-protocol-acme-clients.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ If you run into any issues, please let us know [in GitHub Discussions][gh-discus
## Requirements

- **Open source -** For `step-ca`, this tutorial assumes you have initialized and started up an instance using the steps in [Getting Started](../step-ca/getting-started.mdx). Additionally, you'll need to configure your CA with an ACME provisioner. Run `step ca provisioner add acme --type ACME`, and restart your CA.
- **[Smallstep Certificate Manager](../certificate-manager/acme.mdx) -** this tutorial assumes you have [created a hosted or linked authority](../certificate-manager/getting-started.mdx) and are running a local [ACME Registration Authority](../registration-authorities/acme-for-certificate-manager.mdx).
- **[Smallstep Certificate Manager](../certificate-manager/acme/README.mdx) -** this tutorial assumes you have [created a hosted or linked authority](../certificate-manager/getting-started.mdx) and are running a local [ACME Registration Authority](../registration-authorities/acme-for-certificate-manager.mdx).

## Overview

Expand Down