diff --git a/.ansible-sign/sha256sum.txt b/.ansible-sign/sha256sum.txt
index db213a5..45d5603 100644
--- a/.ansible-sign/sha256sum.txt
+++ b/.ansible-sign/sha256sum.txt
@@ -89,7 +89,7 @@ b64a9ce7ade9b8fae7bda827f7a8d179809a8df065c8bafc1af07ae827ffb2aa  SNOWSetup/imag
 3b6b1d02322d2b0435b86bec366c94c6fe928ab84f0d2b881cf102021c44dddc  SNOWSetup/images/workflow_start.jpg
 cb3a760e0f134314711929e87e54b3a46d3d4898f0baa2d641000ee1e3b63708  SNOWSetup/images/write_scope.png
 b8bc0e6865c91d1d8cedf5bc9faa24782629806c15f99d0b24e3397ec294dcbb  SNOWSetup/images/write_scope_deets.png
-fade46545249da21946d3b675cb5369d414f8d32b38008fc55598ea820801f46  SNOWSetup/readme.md
+64e1d129d6748ce068523394aee4af7a84e467b7efcdcb86c6fb0ff18951932e  SNOWSetup/readme.md
 8d64a90e1cf927f9adf8074d405a62ec50f4df417865706d1f4bc5ff5bdfeaa5  ServiceNowCR_and_approve.yml
 db0cf6bab374ea48077c3898aea1602a570541a49ed82797b7459c9ce9a9824c  ServiceNowCR_canceled.yml
 675d62c62ed528e495f8144290d181875521766c5cebb9661fc15552f1db1083  ServiceNowCR_closed.yml
diff --git a/.ansible-sign/sha256sum.txt.sig b/.ansible-sign/sha256sum.txt.sig
index f2c672b..b279c16 100644
--- a/.ansible-sign/sha256sum.txt.sig
+++ b/.ansible-sign/sha256sum.txt.sig
@@ -1,14 +1,14 @@
 -----BEGIN PGP SIGNATURE-----
 
-iQGzBAABCAAdFiEE/bJvyFHKKJdaZDOLTiIiIXrUDNEFAmW5GpgACgkQTiIiIXrU
-DNHaiAv7BvzuW8/YQI7LuB7cnudSMEKH5O0Aq81WKiMMIyEKC2PZ1vUGVee+Yxkw
-SanJFraFMMzIAN3/glNaiSUjMaFeVrtLppfKV9kNXw5UNcbG5Jz1sreasYSYDlph
-gGbo7Y3i+TOdf1BgNvlr6fG1WfhNHsQWWBwZLuEWKexLgSSbqhr/uOC695Q8bvTN
-pR4Yo+3rrfTfSh7iM0SJEmGZqqyAeMMUKtPiwgNgbBUCYKiDq6rgBVpYH/QjC70x
-ah3o6Tbl10483ugg5lFZGHKRtkyFUjNaBdiixk05Kvi/VcQTcqvdwXMTgrpnlLzZ
-2IKJ7m/bbe57V9lSJmTV1RUj5Ex7u5hJqqw+BxElrXISmJLeXzpf8GGHPLr3oi0h
-kMFxk8ztPKvbR8t7dLvuuI1AlWEJRWIPKp2p1b/a71+HlCS5wKzJEkWaOr7LNuQH
-qViHXIr4CWpD4Chhk6l0HPZJz/kNl2NvBkOYi8T8a5OsY1nZm4xBWYQ3LuEQxhty
-teeR7VkJ
-=azo/
+iQGzBAABCAAdFiEE/bJvyFHKKJdaZDOLTiIiIXrUDNEFAmW87HsACgkQTiIiIXrU
+DNFlgwwAm4WwP4bN/af4hGVAJe1w6d21THM9ahIkxDU214yhjxwrduiRoYut/V8S
+wbYV2fxM97YLh1kfVhciWKRlye/3H8xaDK1N3W8xydj13vC5bYHjkvyKoOhrKkvn
+nn8YuIleiZ8jBkUxfH7sFhee3P9PNy7kw2vSHG0YKBZRBDhZWbledS3mAIUzRcQp
++8SRgtAurAumdFEZFWLk6Kc1ZujikRaw8iOqJK4864AJ5eS4qsOTF2cdkATCbuzb
+nMrAPvRyV4D4xB50zBOvqTUIgu/5VV8/9Lj4Smp36NASCwUt86fqRAD3IRM5yAaP
+RMLWzbHH1mV77G7vnjPoHw0DT5ri1cRCE+CBIfy/3rdqkGHHx3E6cLfcCb4GRnlN
+J0Hi+niP1CWcSjcIfNzfWA1G2hCj9DrbL0wny0Awhw4phGeG+W3zixPdgBgXMc/k
+bPE/J6c11LiyWOnbwh/vpILTAgOvpnfrzSsl1xcZnSXXVONUU7bxxNqvMWdRcDCS
+/uyTMgJc
+=a6c7
 -----END PGP SIGNATURE-----
diff --git a/SNOWSetup/readme.md b/SNOWSetup/readme.md
index a2704ec..647103e 100644
--- a/SNOWSetup/readme.md
+++ b/SNOWSetup/readme.md
@@ -25,6 +25,9 @@
 
 ## ServiceNow/AAP Integration Instructions using Rest Messages
 
+## Notes
+- ServiceNow MID Servers do not support OAuth, you must use basic authentication. Skip steps 1-3, 6-11. In step 12, click Authentication Type of Basic. Click the Magnifying Glass next to the Basic Auth Profile and create a new profile with a valid AAP username and password. Skip step 13. In step 14, under HTTP Request, ensure you select the desired MID Server next to Use MID Server.
+
 ### Preparing AAP
 
 #### 1)
@@ -288,7 +291,10 @@ Congratulations! After completing these steps, you can now use a ServiceNow Cata
 
 ## ServiceNow/AAP Integration Instructions using Ansible Spoke
 
-This walkthrough assumes you have an Integration Hub Standard/Professional subscription and Ansible spoke activated. It also assumes you have the ability to reach your automation controller from ServiceNow (a mid-server can be utilized). For this example, I will be utilizing an already existing Ansible Automation Platform (AAP) workflow that patches all of my Red Hat Enterprise Linux Servers and updates a ServiceNow Catalog Request. I will also be using Ansible Automation Platform 2.2 but this integration will work in Ansible Automation Platform 1.2 and 2.1 as well. Ansible spoke leverages the ServiceNow Flow Designer which can be easier to use when leveraging variables and building out the API Rest message.
+This walkthrough assumes you have an Integration Hub Standard/Professional subscription and Ansible spoke activated. It also assumes you have the ability to reach your automation controller from ServiceNow (a mid-server can be utilized but only basic Auth will work). For this example, I will be utilizing an already existing Ansible Automation Platform (AAP) workflow that patches all of my Red Hat Enterprise Linux Servers and updates a ServiceNow Catalog Request. I will also be using Ansible Automation Platform 2.2 but this integration will work in Ansible Automation Platform 1.2 and any version of 2.x as well. Ansible spoke leverages the ServiceNow Flow Designer which can be easier to use when leveraging variables and building out the API Rest message.
+
+## Notes
+- ServiceNow MID Servers do not support OAuth, you must use basic authentication. Skip steps 1-3 and replace steps 6 and 7 with https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/integrationhub-store-spokes/task/setup-ansible.html#setup-ansiblespk-basic
 
 ### Preparing AAP
 
@@ -337,6 +343,8 @@ Click the **Submit** (or **Update** if you had a previous AAP certificate) butto
 
 ### Set Up Ansible Spoke
 
+If using a MID server, skip steps 6 and 7 and perform https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/integrationhub-store-spokes/task/setup-ansible.html#setup-ansiblespk-basic
+
 #### 6)
 Navigate to **Connections & Credentials-->Connection & Credential Aliases**. Click the existing "AnsibleTowerAlias" alias. In the resulting dialog window, ensure the following fields are filled in: