diff --git a/graphics/workspace-one-api-panel.png b/graphics/workspace-one-api-panel.png new file mode 100644 index 00000000..54069d1e Binary files /dev/null and b/graphics/workspace-one-api-panel.png differ diff --git a/step-ca/basic-certificate-authority-operations.mdx b/step-ca/basic-certificate-authority-operations.mdx index 4ac5a6c5..df8d2a87 100644 --- a/step-ca/basic-certificate-authority-operations.mdx +++ b/step-ca/basic-certificate-authority-operations.mdx @@ -1,4 +1,5 @@ --- +updated_at: May 19, 2025 title: Basic Certificate Authority Operations html_title: basic certificate authority operations description: Learn about the basic certificate authority operations of step-ca @@ -229,7 +230,7 @@ In this section we'll go over the basics of issuing and renewing SSH certificate ### Background SSH certificates are not X.509 certificates. -Instead, they follow an [SSH-specific certificate format](https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.certkeys). +Instead, they follow an [SSH-specific certificate format](https://datatracker.ietf.org/doc/draft-miller-ssh-cert/). Mercifully, they are a lot simpler than X.509: - SSH supports only User certificates and Host certificates. diff --git a/tutorials/acme-protocol-acme-clients.mdx b/tutorials/acme-protocol-acme-clients.mdx index 70c3df5e..944ad9c6 100644 --- a/tutorials/acme-protocol-acme-clients.mdx +++ b/tutorials/acme-protocol-acme-clients.mdx @@ -1,4 +1,5 @@ --- +updated_at: May 19, 2025 title: Configure popular ACME clients to use a private CA with the ACME protocol html_title: Configure ACME clients to use a private CA with the ACME protocol description: Connect popular ACME clients to a private ACME server with this ACME protocol client configuration tutorial. @@ -217,7 +218,7 @@ sudo LEGO_CA_CERTIFICATES="$(step path)/certs/root_ca.crt" \ -s https://ca.internal/acme/acme/directory --http run ``` -Like `certbot`, `lego` can solve the `http-01` challenge in [_standalone_ mode](https://go-acme.github.io/lego/usage/cli/obtain-a-certificate/index.html#using-the-built-in-web-server) and [_webroot_ mode](hhttps://go-acme.github.io/lego/usage/cli/obtain-a-certificate/index.html#using-an-existing-running-web-server). +Like `certbot`, `lego` can solve the `http-01` challenge in [_standalone_ mode](https://go-acme.github.io/lego/usage/cli/obtain-a-certificate/index.html#using-the-built-in-web-server) and [_webroot_ mode](https://go-acme.github.io/lego/usage/cli/obtain-a-certificate/index.html#using-an-existing-running-web-server). It can also solve the `dns-01` challenge for [many DNS providers](https://go-acme.github.io/lego/dns/index.html). You can [renew the certificates](https://go-acme.github.io/lego/usage/cli/renew-a-certificate/index.html) you've installed using `lego` by running: diff --git a/tutorials/connect-workspace-one-to-smallstep.mdx b/tutorials/connect-workspace-one-to-smallstep.mdx index b57c2fe4..bc1f70e6 100644 --- a/tutorials/connect-workspace-one-to-smallstep.mdx +++ b/tutorials/connect-workspace-one-to-smallstep.mdx @@ -1,5 +1,5 @@ --- -updated_at: May 14, 2025 +updated_at: May 19, 2025 title: Connect Workspace One UEM to Smallstep html_title: Connect Workspace One to Smallstep description: Configure Workspace One UEM to deploy the Smallstep Agent and distribute certificates and configuration to clients. @@ -28,7 +28,7 @@ First, we’ll create a scoped API role for Smallstep: 2. Create a role named “Smallstep” with a description of “Smallstep Integration” 3. Smallstep needs Read access to Devices, using the REST API. Choose API → REST on the left, and choose ✅ Read for the row “Devices” - ![Workspace ONE API Panel](workspace-one/api-panel.png) + ![Workspace ONE API Panel](workspace-one-api-panel.png) 4. Choose **Save** @@ -125,7 +125,7 @@ In this step, we’ll tie everything together by creating Windows policy to enro - Challenge Basic Authentication Username - Challenge Basic Authentication Password - If you need to retrieve these again, you can always visit: [**Settings → Device Management](https://smallstep.com/app/?next=/settings/devices) → Omnissa Workspace ONE** + If you need to retrieve these again, you can always visit: **[Settings → Device Management](https://smallstep.com/app/?next=/settings/devices) → Omnissa Workspace ONE** #### Add a Workspace ONE CA resource diff --git a/tutorials/wifi-setup-guide.mdx b/tutorials/wifi-setup-guide.mdx index c8651271..fd713f69 100644 --- a/tutorials/wifi-setup-guide.mdx +++ b/tutorials/wifi-setup-guide.mdx @@ -1,6 +1,6 @@ --- title: Configure 802.1x EAP-TLS WPA-Enterprise Wi-Fi on your Access Point -updated_at: March 11, 2024 +updated_at: May 19, 2025 html_title: Configure your Wi-Fi Access Point to use Enterprise EAP-TLS certificate-based authentication with Smallstep description: This tutorial describes how to set up Smallstep's certificate-based Wi-Fi on several popular Access Point models --- @@ -171,7 +171,7 @@ Your 802.1x EAP-TLS WPA-Enterprise Wi-Fi network is ready for use. ## Configure 802.1x EAP-TLS WPA-Enterprise Wi-Fi on Aruba -*Note: These instructions follow setup for Aruba mobility controllers wireless AP portals. See [Aruba reference WLAN configuration documentation](https://www.arubanetworks.com/techdocs/ArubaOS_86_Web_Help/Content/arubaos-solutions/virtual-ap/basi-wlan-conf-work.htm)* +*Note: These instructions follow setup for Aruba mobility controllers wireless AP portals. See [Aruba reference WLAN configuration documentation](https://arubanetworking.hpe.com/techdocs/ArubaOS_8.12.0_Web_Help/Content/arubaos-solutions/virtual-ap/wlan-conf-prof.htm)* First, create a new RADIUS profile: