From 6ebaf90202a28c144dff432f8c49f8e551f10c49 Mon Sep 17 00:00:00 2001
From: James Royal <jroyal@cloudflare.com>
Date: Mon, 11 Apr 2022 15:39:18 -0500
Subject: [PATCH 1/2] [Access] Remove instructions that required jq and lokey

---
 .../identity/users/validating-json.md         | 24 +++----------------
 1 file changed, 3 insertions(+), 21 deletions(-)

diff --git a/content/cloudflare-one/identity/users/validating-json.md b/content/cloudflare-one/identity/users/validating-json.md
index c34ea53b0e8..b042a409260 100644
--- a/content/cloudflare-one/identity/users/validating-json.md
+++ b/content/cloudflare-one/identity/users/validating-json.md
@@ -23,31 +23,13 @@ You can use the JWT created by Cloudflare Access to validate requests on your or
 
 ## Manual verification
 
-{{<Aside>}}
-
-<b>Before you start</b>
-
-Install [`lokey`](https://github.com/jpf/lokey) and [`jq`](https://stedolan.github.io/jq/download/).
-
-{{</Aside>}}
-
-1.  Run this command:
-
-    ```bash
-    curl -s https://<your team domain>/cdn-cgi/access/certs | jq .keys[0] | lokey to pem -----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA01SvMv4TgFIECQgzHaRL DGVaKhRQHjgdiSOpbqhHQMdcNtBIM0HAQbrs7YS6sQCCdZC5wCvlq3xgqdU5J6k YI5OCSsIWXKkobAl6PbXHdN0bJximeiHGa3O0hMREP6RKBoI6ayNmZ3WlVGWY 6ie47KGqN69l7fPKyZvszb4GdpxE0r8gllZZwIuPjzlghXRlrkaP48ucQwo+tq PSSdDdW57TCFmy+G547W5iWZWJIeNkfVu9t6FktvCwSZ1ekum3X7IQcd0O0DWSR Aj9tzNDPkzOeSFxmQkKpWs8Qw7ZBIfLOsO3DCH6VPNhS2cqhw1AAMunh8alDKQU aQIDAQAB -----END PUBLIC KEY-----
-    ```
-
-    If an error occurs while running `lokey`, install the [Python six](https://pypi.python.org/pypi/six) library, and try again:
-
-    ```sh
-    $ pip install six==1.10.0
-    ```
-
 1.  Go to [jwt.io](https://jwt.io/).
 
 1.  Select the RS256 algorithm.
 
-1.  Paste the JWT into the field on the left.
+1.  Paste the JWT into the field on the left. Get the `kid` value of the header box on the decoded column.
+
+1.  Get your public key by going to `https://<your team domain>/cdn-cgi/access/certs` and copy the cert value of the block in `public_certs` with the `kid` value you found in the previous step.
 
 1.  Enter the public key in the **Public Key** field.
 

From 6d9df8bca700961e279f2ba6422475d32a7bd2f4 Mon Sep 17 00:00:00 2001
From: James Royal <jroyal@cloudflare.com>
Date: Tue, 12 Apr 2022 14:51:54 -0500
Subject: [PATCH 2/2] [Access] Updated with review recommendations

---
 .../cloudflare-one/identity/users/validating-json.md   | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/content/cloudflare-one/identity/users/validating-json.md b/content/cloudflare-one/identity/users/validating-json.md
index b042a409260..6a71689dfc5 100644
--- a/content/cloudflare-one/identity/users/validating-json.md
+++ b/content/cloudflare-one/identity/users/validating-json.md
@@ -27,11 +27,15 @@ You can use the JWT created by Cloudflare Access to validate requests on your or
 
 1.  Select the RS256 algorithm.
 
-1.  Paste the JWT into the field on the left. Get the `kid` value of the header box on the decoded column.
+1.  Paste the JWT into the **Encoded** field on the left. Get the `kid` value of the header box on the decoded column.
 
-1.  Get your public key by going to `https://<your team domain>/cdn-cgi/access/certs` and copy the cert value of the block in `public_certs` with the `kid` value you found in the previous step.
+1.  Get your public key:
 
-1.  Enter the public key in the **Public Key** field.
+    1. Go to `https://<your team domain>/cdn-cgi/access/certs`.
+    2. Under `public_certs`, locate the entry with the `kid` value you found in Step #3.
+    3. Copy the `cert` value.
+
+1.  In the **Verify Signature** box, paste the `cert` value into the **Public Key** field.
 
 1.  Ensure that the signature says **verified**.