@@ -182,10 +182,11 @@ Take note of your `TenantId` if applicable for your situation. The `TenantId` ca
182182
183183OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects. This provider was originally built against CoreOS Dex and we will use it as an example.
184184
185−1. Launch a Dex instance using the [getting started guide](https://github.com/coreos/dex/blob/master/Documentation/getting-started.md).
186−2. Setup oauth2-proxy with the correct provider and using the default ports and callbacks.
187−3. Login with the fixture use in the dex guide and run the oauth2-proxy with the following args:
185+1. Launch a Dex instance using the [getting started guide](https://github.com/coreos/dex/blob/master/Documentation/getting-started.md).
186+2. Setup oauth2-proxy with the correct provider and using the default ports and callbacks.
187+3. Login with the fixture use in the dex guide and run the oauth2-proxy with the following args:
188188
189+```
189190 -provider oidc
190191 -provider-display-name "My OIDC Provider"
191192 -client-id oauth2-proxy
@@ -194,6 +195,7 @@ OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many ma
194195 -oidc-issuer-url http://127.0.0.1:5556
195196 -cookie-secure=false
196197 -email-domain example.com
198+```
197199
198200The OpenID Connect Provider (OIDC) can also be used to connect to other Identity Providers such as Okta. To configure the OIDC provider for Okta, perform
199201the following steps: