From 416c8b0a5c2e82c41489e9cab91e28a0eeaf9392 Mon Sep 17 00:00:00 2001 From: Jonathan Herlin Date: Mon, 6 Jul 2020 12:04:16 +0200 Subject: [PATCH] Make example args a codeblock Making this a code block aligns with the rest of the examples and makes it easier to read --- docs/2_auth.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/2_auth.md b/docs/2_auth.md index 46d33c3a..8b7c3660 100644 --- a/docs/2_auth.md +++ b/docs/2_auth.md @@ -182,10 +182,11 @@ Take note of your `TenantId` if applicable for your situation. The `TenantId` ca OpenID 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. -1. Launch a Dex instance using the [getting started guide](https://github.com/coreos/dex/blob/master/Documentation/getting-started.md). -2. Setup oauth2-proxy with the correct provider and using the default ports and callbacks. -3. Login with the fixture use in the dex guide and run the oauth2-proxy with the following args: +1. Launch a Dex instance using the [getting started guide](https://github.com/coreos/dex/blob/master/Documentation/getting-started.md). +2. Setup oauth2-proxy with the correct provider and using the default ports and callbacks. +3. Login with the fixture use in the dex guide and run the oauth2-proxy with the following args: +``` -provider oidc -provider-display-name "My OIDC Provider" -client-id oauth2-proxy @@ -194,6 +195,7 @@ OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many ma -oidc-issuer-url http://127.0.0.1:5556 -cookie-secure=false -email-domain example.com +``` The 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 the following steps: