From eba63f1359642d1c352121e0ba05b8de23f1d05e Mon Sep 17 00:00:00 2001
From: James Elliott <james-d-elliott@users.noreply.github.com>
Date: Sun, 27 Nov 2022 16:07:08 +1100
Subject: [PATCH] docs: update index (#4437)

---
 .../authorization/openid-connect-1.0.md       | 21 +++++++++++++++++++
 .../overview/authorization/trusted-headers.md | 20 ++++++++++++++++++
 docs/layouts/index.html                       |  2 +-
 3 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 docs/content/en/overview/authorization/openid-connect-1.0.md
 create mode 100644 docs/content/en/overview/authorization/trusted-headers.md

diff --git a/docs/content/en/overview/authorization/openid-connect-1.0.md b/docs/content/en/overview/authorization/openid-connect-1.0.md
new file mode 100644
index 000000000..53f7637c0
--- /dev/null
+++ b/docs/content/en/overview/authorization/openid-connect-1.0.md
@@ -0,0 +1,21 @@
+---
+title: "OpenID Connect 1.0"
+description: "OpenID Connect 1.0 is a authorization identity framework supported by Authelia."
+date: 2022-06-15T17:51:47+10:00
+draft: false
+images: []
+menu:
+  overview:
+    parent: "authorization"
+weight: 330
+toc: false
+---
+
+[OpenID Connect 1.0](https://openid.net/connect/) is a authorization identity framework supported by Authelia. You can
+configure your applications to use Authelia as an [OpenID Connect 1.0 Provider](https://openid.net/connect/). We do not
+currently operate as an [OpenID Connect 1.0 Relying Party](https://openid.net/connect/). This like all single-sign on
+technologies requires support by the protected application.
+
+See the [OpenID Connect 1.0 Configuration Guide](../../configuration/identity-providers/open-id-connect.md) and the
+[OpenID Connect 1.0 Integration Guide](../../integration/openid-connect/introduction.md) for more information.
+
diff --git a/docs/content/en/overview/authorization/trusted-headers.md b/docs/content/en/overview/authorization/trusted-headers.md
new file mode 100644
index 000000000..c99122f9b
--- /dev/null
+++ b/docs/content/en/overview/authorization/trusted-headers.md
@@ -0,0 +1,20 @@
+---
+title: "Trusted Headers SSO"
+description: "Trusted Headers SSO is a simple header authorization framework supported by Authelia."
+lead: "Trusted Headers is a simple header authorization framework supported by Authelia."
+date: 2022-06-15T17:51:47+10:00
+draft: false
+images: []
+menu:
+  overview:
+    parent: "authorization"
+weight: 340
+toc: false
+---
+
+This mechanism is supported by proxies which inject certain response headers from Authelia into the protected
+application. This is a very basic means that allows the target application to identify the user who is logged in
+to Authelia. This like all single-sign on technologies requires support by the protected application.
+
+You can read more about this in the [Trusted Header SSO Integration Guide](../../integration/trusted-header-sso/introduction.md).
+
diff --git a/docs/layouts/index.html b/docs/layouts/index.html
index d300e2493..94f91eef6 100644
--- a/docs/layouts/index.html
+++ b/docs/layouts/index.html
@@ -52,7 +52,7 @@
       <div class="row justify-content-center text-center">
         <div class="col-lg-5">
           <h2 class="h4">Single Sign-On 🎟️</h2>
-          <p>Allow your users the convenience of just being required to login once to a wide range of web applications.</p>
+          <p>Allow your users the convenience of just being required to login once to a wide range of web applications via <a href="./overview/authorization/openid-connect-1.0/">OpenID Connect 1.0</a> or <a href="./overview/authorization/trusted-headers/">Trusted Headers</a></p>
         </div>
         <div class="col-lg-5">
           <h2 class="h4">Authorization Policies 👮</h2>