doc: fix formatting issue in Google provider doc (#2907)
A missing line break caused subsequent list items to be squished into a single paragraph.
commit60570cc60e593e3e2b31019ad385e810f3d01dfd
authorJon Newton <newt@hey.com>
dateWed 8 Jan 2025, 19:51 (2 years ago)
parent5df6053
docs/docs/configuration/providers/google.md+1
@@ -59,6 +59,7 @@ account is still authorized.
5959 of this flag with different groups and the user will be checked against all the provided groups.
6060
6161(Only if using a JSON file (see step 1))
62+
62639. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
6364 set the path to the file in the `google-service-account-json` flag.
646510. Restart oauth2-proxy.
docs/versioned_docs/version-7.6.x/configuration/providers/google.md+1
@@ -59,6 +59,7 @@ account is still authorized.
5959 of this flag with different groups and the user will be checked against all the provided groups.
6060
6161(Only if using a JSON file (see step 1))
62+
62639. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
6364 set the path to the file in the `google-service-account-json` flag.
646510. Restart oauth2-proxy.
docs/versioned_docs/version-7.7.x/configuration/providers/google.md+1
@@ -59,6 +59,7 @@ account is still authorized.
5959 of this flag with different groups and the user will be checked against all the provided groups.
6060
6161(Only if using a JSON file (see step 1))
62+
62639. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
6364 set the path to the file in the `google-service-account-json` flag.
646510. Restart oauth2-proxy.