docs: fix gitea example (#5156)

Fixes the gitea example and a few other minor issues.

Signed-off-by: James Elliott <james-d-elliott@users.noreply.github.com>

docs/content/en/integration/openid-connect/apache-guacamole/index.md

@@ -57,6 +57,11 @@ The following YAML configuration is an example __Authelia__
 [Apache Guacamole] which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: guacamole
       description: Apache Guacamole
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/argocd/index.md

@@ -60,6 +60,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: argocd
       description: Argo CD
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/bookstack/index.md

@@ -62,6 +62,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: bookstack
       description: BookStack
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/cloudflare-zerotrust/index.md

@@ -70,6 +70,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: cloudflare
       description: Cloudflare ZeroTrust
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/firezone/index.md

@@ -71,6 +71,11 @@ The following YAML configuration is an example __Authelia__
 will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: firezone
       description: Firezone
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/gitea/index.md

@@ -81,6 +81,11 @@ The following YAML configuration is an example __Authelia__
 will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: gitea
       description: Gitea
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
@@ -97,9 +102,9 @@ will operate with the above example:
 
 ## See Also
 
-- [Gitea] app.ini [Config Cheat Sheet - OpenID](https://docs.gitea.io/en-us/config-cheat-sheet/#openid-openid)
+- [Gitea] app.ini [Config Cheat Sheet](https://docs.gitea.io/en-us/config-cheat-sheet):
-- [Gitea] app.ini [Config Cheat Sheet - Service](https://docs.gitea.io/en-us/config-cheat-sheet/#service-service)
+  - [OpenID](https://docs.gitea.io/en-us/config-cheat-sheet/#openid-openid)
+  - [Service](https://docs.gitea.io/en-us/config-cheat-sheet/#service-service)
 
-- [Authelia]: https://www.authelia.com
 [Gitea]: https://gitea.io/
 [OpenID Connect 1.0]: ../../openid-connect/introduction.md

docs/content/en/integration/openid-connect/gitlab/index.md

@@ -73,6 +73,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: gitlab
       description: GitLab
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/grafana/index.md

@@ -91,6 +91,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: grafana
       description: Grafana
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/harbor/index.md

@@ -64,6 +64,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: harbor
       description: Harbor
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/hashicorp-vault/index.md

@@ -47,6 +47,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: vault
       description: HashiCorp Vault
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/komga/index.md

@@ -69,6 +69,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: komga
       description: Komga
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/minio/index.md

@@ -67,6 +67,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: minio
       description: MinIO
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/misago/index.md

@@ -15,10 +15,10 @@ community: true
 
 ## Tested Versions
 
--   [Authelia](https://www.authelia.com)
+* [Authelia](https://www.authelia.com)
-    -   [v4.37.5](https://github.com/authelia/authelia/releases/tag/v4.37.5)
+  * [v4.37.5](https://github.com/authelia/authelia/releases/tag/v4.37.5)
--   [Misago](https://github.com/rafalp/Misago)
+* [Misago](https://github.com/rafalp/Misago)
-    -   [misago-image v0.29.1](https://github.com/tetricky/misago-image/releases/tag/v0.29.1)
+  * [misago-image v0.29.1](https://github.com/tetricky/misago-image/releases/tag/v0.29.1)
 
 ## Before You Begin
 
@@ -82,6 +82,10 @@ To configure [Misago] to utilize Authelia as an [OpenID Connect 1.0](https://www
 The following YAML configuration is an example **Authelia** [client configuration](https://www.authelia.com/configuration/identity-providers/open-id-connect/#clients) for use with [Misago] which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
     clients:
     - id: misago
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/nextcloud/index.md

@@ -85,6 +85,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: nextcloud
       description: NextCloud
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/outline/index.md

@@ -64,6 +64,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: outline
       description: Outline
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/portainer/index.md

@@ -65,6 +65,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: portainer
       description: Portainer
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/proxmox/index.md

@@ -22,14 +22,9 @@ aliases:
 * [Proxmox]
   * 7.1-10
 
-### Common Notes
+## Before You Begin
 
-1. You are *__required__* to utilize a unique client id for every client.
+{{% oidc-common %}}
-2. The client id on this page is merely an example and you can theoretically use any alphanumeric string.
-3. You *__should not__* use the client secret in this example, We *__strongly recommend__* reading the
-   [Generating Client Secrets] guide instead.
-
-[Generating Client Secrets]: ../specific-information.md#generating-client-secrets
 
 ### Specific Notes
 
@@ -74,6 +69,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: proxmox
       description: Proxmox
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/seafile/index.md

@@ -73,6 +73,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: seafile
       description: Seafile
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/specific-information.md

@@ -46,9 +46,11 @@ which case the secret should be encrypted and not be stored in plaintext. The mo
 client configurations will be stored in the database with the secret both salted and peppered.
 
 Authelia currently does not implement any of the specifications or protocols which require secrets being accessible in
-the clear and currently has no plans to implement any of these. As such it's *__strongly discouraged and heavily
+the clear such as most notibly the `client_secret_jwt` grant and currently we no plans to implement any of these. As
-deprecated__* and we instead recommended that users remove this from their configuration entirely and use the
+such it's *__strongly discouraged and heavily deprecated__* and we instead recommended that users remove this from their
-[Generating Client Secrets](#generating-client-secrets) guide.
+configuration entirely and use the [Generating Client Secrets](#generating-client-secrets) guide. At such a time as we
+support one of these protocols we will very likely only allow plaintext for clients configured expressly for this
+purpose i.e. a client that only allows `client_secret_jwt` and no other grants.
 
 Plaintext is either denoted by the `$plaintext$` prefix where everything after the prefix is the secret. In addition if
 the secret does not start with the `$` character it's considered as a plaintext secret for the time being but is

docs/content/en/integration/openid-connect/synapse/index.md

@@ -67,6 +67,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: synapse
       description: Synapse
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.

docs/content/en/integration/openid-connect/synology-dsm/index.md

@@ -69,6 +69,11 @@ The following YAML configuration is an example __Authelia__
 which will operate with the above example:
 
 ```yaml
+identity_providers:
+  oidc:
+    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
+    ## See: https://www.authelia.com/c/oidc
+    clients:
     - id: synology-dsm
       description: Synology DSM
       secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.