From 234d2adad4f75a0d8a1346c1ea956066a60f39f1 Mon Sep 17 00:00:00 2001 From: Carl Tashian Date: Wed, 2 Sep 2026 14:17:28 -0700 Subject: [PATCH] Tutorials: get the Authority ID from the authority detail page Certificate Manager now shows the Authority ID directly on the authority detail page, alongside the root certificate download. Replace the List Authorities API calls in the wired, wireless, and GitHub SSH tutorials with a pointer to that page. The wired tutorial previously told readers to save the root certificate but never showed how; Step 2 then used client_ca.crt. The download link on the detail page closes that gap. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01Ls5vRnPQF7bFoaNueQc54h --- tutorials/protect-github-ssh.mdx | 14 ++++-------- tutorials/protect-wired-networks.mdx | 17 +++++--------- tutorials/protect-wireless-networks.mdx | 30 +++++++------------------ 3 files changed, 18 insertions(+), 43 deletions(-) diff --git a/tutorials/protect-github-ssh.mdx b/tutorials/protect-github-ssh.mdx index f7219cef..fd949dda 100644 --- a/tutorials/protect-github-ssh.mdx +++ b/tutorials/protect-github-ssh.mdx @@ -1,5 +1,5 @@ --- -updated_at: July 08, 2026 +updated_at: September 02, 2026 title: Protect GitHub with SSH Certificates html_title: Protect GitHub Repositories with Hardware-Bound SSH Certificates description: Authenticate to GitHub with short-lived SSH certificates backed by your device's TPM or Secure Enclave, issued and managed by the Smallstep Agent. @@ -117,15 +117,9 @@ echo "Authorization: Bearer [your API token]" > api_headers set -o history ``` -Find the authority that should issue your SSH certificates with the -[List Authorities](https://gateway.smallstep.com/v2025-01-01/operations/GetAuthorities) endpoint: - -```bash -curl -sH @api_headers --request GET \ - --url https://gateway.smallstep.com/api/authorities \ - --header 'Accept: application/json' \ - --header 'x-smallstep-api-version: 2025-01-01' | jq '.[] | {id, name, domain}' -``` +Next, choose the SSH authority that should issue your SSH certificates. +In the Smallstep dashboard, go to **Certificate Manager → Authorities**, open the authority, +and copy its **Authority ID** from the **Authority Settings** panel. Then create the credential with the [Create Credential](https://gateway.smallstep.com/v2025-01-01/operations/PostCredentials) endpoint: diff --git a/tutorials/protect-wired-networks.mdx b/tutorials/protect-wired-networks.mdx index d31a1a6d..21cb7ca7 100644 --- a/tutorials/protect-wired-networks.mdx +++ b/tutorials/protect-wired-networks.mdx @@ -1,5 +1,5 @@ --- -updated_at: July 08, 2026 +updated_at: September 02, 2026 title: Protect Wired Networks with 802.1X EAP-TLS html_title: Protect Wired Networks with 802.1X EAP-TLS Certificates and Smallstep description: Set up certificate-based Ethernet access. Issue client certificates via the Smallstep API, configure RADIUS and your switches, and deploy to clients. @@ -47,16 +47,11 @@ echo "Authorization: Bearer [your API token]" > api_headers set -o history ``` -Find the authority that should issue your client certificates with the -[List Authorities](https://gateway.smallstep.com/v2025-01-01/operations/GetAuthorities) endpoint, -and save its `id` and `root` certificate: - -```bash -curl -sH @api_headers --request GET \ - --url https://gateway.smallstep.com/api/authorities \ - --header 'Accept: application/json' \ - --header 'x-smallstep-api-version: 2025-01-01' | jq '.[] | {id, name, domain}' -``` +Next, choose the authority that should issue your client certificates. +In the Smallstep dashboard, go to **Certificate Manager → Authorities** and open the authority. +From the **Authority Settings** panel, copy the **Authority ID**, +and download the **Root Certificate** as `client_ca.crt`. +You'll register the root certificate with your RADIUS server in Step 2. Then create the credential with the [Create Credential](https://gateway.smallstep.com/v2025-01-01/operations/PostCredentials) endpoint: diff --git a/tutorials/protect-wireless-networks.mdx b/tutorials/protect-wireless-networks.mdx index 2a4a3c99..990321bc 100644 --- a/tutorials/protect-wireless-networks.mdx +++ b/tutorials/protect-wireless-networks.mdx @@ -1,5 +1,5 @@ --- -updated_at: July 08, 2026 +updated_at: September 02, 2026 title: Protect Wireless Networks with 802.1X EAP-TLS html_title: Protect Wireless Networks with 802.1X EAP-TLS Certificates and Smallstep description: Set up certificate-based Wi-Fi end to end. Issue client certificates via the Smallstep API, configure RADIUS and access points, and deploy to clients. @@ -100,29 +100,15 @@ set -o history ## Find your authority Certificates are issued by one of your team's X.509 authorities. -Use the [List Authorities](https://gateway.smallstep.com/v2025-01-01/operations/GetAuthorities) endpoint to find the authority -that should issue your Wi-Fi client certificates: +In the Smallstep dashboard, go to **Certificate Manager → Authorities** +and open the authority that should issue your Wi-Fi client certificates. -```bash -curl -sH @api_headers --request GET \ - --url https://gateway.smallstep.com/api/authorities \ - --header 'Accept: application/json' \ - --header 'x-smallstep-api-version: 2025-01-01' | jq '.[] | {id, name, domain}' -``` - -Save two values from the authority you choose: - -- The `id`, which you'll use as the `authorityID` when creating the credential. -- The `root` certificate (PEM), which you'll register with your RADIUS server in Step 2 - so it can verify client certificates issued by this authority: +Save two values from the **Authority Settings** panel: -```bash -curl -sH @api_headers --request GET \ - --url https://gateway.smallstep.com/api/authorities \ - --header 'Accept: application/json' \ - --header 'x-smallstep-api-version: 2025-01-01' \ - | jq -r '.[] | select(.id == "[your authority ID]") | .root' > client_ca.crt -``` +- The **Authority ID**, which you'll use as the `authorityID` when creating the credential. +- The **Root Certificate**, which you'll register with your RADIUS server in Step 2 + so it can verify client certificates issued by this authority. + Download it and save it as `client_ca.crt`. ## Create the credential