docs: replace httpbin with verify (#1702)

Signed-off-by: Bobby DeSimone <bobbydesimone@gmail.com>

docs/guides/cloud-run.md

@@ -108,7 +108,7 @@ And a hello page:
 
 If your target application is not running on GCP, you can also perform your own header validation.
 
-Browse to [https://httpbin.cloudrun.pomerium.io](https://httpbin.cloudrun.pomerium.io/headers)
+Browse to [https://verify.cloudrun.pomerium.io](https://verify.cloudrun.pomerium.io/headers)
 
 You should see your identity header set:
 

docs/guides/local-oidc.md

@@ -34,8 +34,8 @@ services:
     depends_on:
       - identityprovider
 
-  httpbin:
-    image: kennethreitz/httpbin:latest
+  verify:
+    image: pomerium/verify
     expose:
       - 80
 
@@ -75,8 +75,8 @@ cookie_secret: <reducted>
 
 # https://www.pomerium.io/configuration/#policy
 policy:
-  - from: https://httpbin.localhost.pomerium.io
-    to: http://httpbin
+  - from: https://verify.localhost.pomerium.io
+    to: http://verify
     allowed_domains:
       - example.org
 ```
@@ -147,7 +147,7 @@ $ : wait identityprovider up
 $ docker-compose up -d
 ```
 
-Now accessing to `https://httpbin.localhost.pomerium.io` and you will be redireted to OIDC server for authentication.
+Now accessing to `https://verify.localhost.pomerium.io` and you will be redireted to OIDC server for authentication.
 
 [identity provider]: ../docs/identity-providers/
 [qlik/simple-oidc-provider]: https://hub.docker.com/r/qlik/simple-oidc-provider/

docs/guides/mtls.md

@@ -74,8 +74,8 @@ idp_client_id: YOUR_CLIENT_ID
 idp_client_secret: YOUR_SECRET
 
 policy:
-  - from: "https://httpbin.localhost.pomerium.io:8443"
-    to: "https://httpbin.org"
+  - from: "https://verify.localhost.pomerium.io:8443"
+    to: "https://verify.org"
     allow_public_unauthenticated_access: true
 ```
 
@@ -89,7 +89,7 @@ Before visiting the page in your browser we have one final step.
 
 ## Install Client Certificate
 
-Because `https://httpbin.localhost.pomerium.io:8443` now requires a client certificate to be accessed, we first need to install that client certificate in our browser. The following instructions are for Chrome, but client certificates are supported in all major browsers.
+Because `https://verify.localhost.pomerium.io:8443` now requires a client certificate to be accessed, we first need to install that client certificate in our browser. The following instructions are for Chrome, but client certificates are supported in all major browsers.
 
 Go to <chrome://settings/certificates>:
 
@@ -109,6 +109,6 @@ You should see the `org-mkcert development certificate` in the list of your cert
 
 ## Using the Client Certificate
 
-You can now visit **<https://httpbin.localhost.pomerium.io>** and you should be prompted to choose a client certificate:
+You can now visit **<https://verify.localhost.pomerium.io>** and you should be prompted to choose a client certificate:
 
 ![choose client certificate](./img/mtls/05-select-client-certificate.png)

docs/guides/nginx.md

@@ -13,7 +13,7 @@ description: >-
 
 This recipe's sources can be found [on github](https://github.com/pomerium/pomerium/tree/master/examples/nginx)
 
-At the end, you will have a locally running install of [httpbin](https://httpbin.org/) behind nginx with policy enforced by Pomerium.
+At the end, you will have a locally running install of [verify](https://verify.pomerium.com/) behind nginx with policy enforced by Pomerium.
 
 ## Background
 
@@ -72,28 +72,28 @@ Nginx configuration for Pomerium endpoints
 
 <<< @/examples/nginx/pomerium.conf
 
-### Nginx - httpbin
+### Nginx - verify
 
 Nginx configuration for the protected endpoint
 
-<<< @/examples/nginx/httpbin.conf
+<<< @/examples/nginx/verify.conf
 
 ### Docker Compose
 
 <<< @/examples/nginx/docker-compose.yaml
 
-Run `docker-compose up`. After a few seconds, browse to [httpbin.localhost.pomerium.io](https://httpbin.localhost.pomerium.io).
+Run `docker-compose up`. After a few seconds, browse to [verify.localhost.pomerium.io](https://verify.localhost.pomerium.io).
 
-You should be prompted to log in through your IdP and then granted access to the deployed `httpbin` instance.
+You should be prompted to log in through your IdP and then granted access to the deployed `verify` instance.
 
 ## That's it!
 
-Your `httpbin` install is protected by Pomerium.
+Your `verify` install is protected by Pomerium.
 
 ## Adapting
 
 To re-use the configuration in this demo in other contexts:
 
-- Update `httpbin.conf` to reflect the correct forward auth URL in `location @error401`
+- Update `verify.conf` to reflect the correct forward auth URL in `location @error401`
 - Update `pomerium.conf` to reflect the pomerium hostname(s) or IP(s) in `upstream pomerium`
 - Update `pomerium.conf` to reflect your pomerium authenticate and forward auth hostnames in `server_name`