doc: fix formatting issue in Google provider doc (#2907)

A missing line break caused subsequent list items to be squished into a single paragraph.
This commit is contained in:
Jon Newton 2025-01-08 19:51:20 -05:00 committed by GitHub
parent 5df6053280
commit 60570cc60e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 0 deletions

View File

@ -59,6 +59,7 @@ account is still authorized.
of this flag with different groups and the user will be checked against all the provided groups. of this flag with different groups and the user will be checked against all the provided groups.
(Only if using a JSON file (see step 1)) (Only if using a JSON file (see step 1))
9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and 9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
set the path to the file in the `google-service-account-json` flag. set the path to the file in the `google-service-account-json` flag.
10. Restart oauth2-proxy. 10. Restart oauth2-proxy.

View File

@ -59,6 +59,7 @@ account is still authorized.
of this flag with different groups and the user will be checked against all the provided groups. of this flag with different groups and the user will be checked against all the provided groups.
(Only if using a JSON file (see step 1)) (Only if using a JSON file (see step 1))
9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and 9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
set the path to the file in the `google-service-account-json` flag. set the path to the file in the `google-service-account-json` flag.
10. Restart oauth2-proxy. 10. Restart oauth2-proxy.

View File

@ -59,6 +59,7 @@ account is still authorized.
of this flag with different groups and the user will be checked against all the provided groups. of this flag with different groups and the user will be checked against all the provided groups.
(Only if using a JSON file (see step 1)) (Only if using a JSON file (see step 1))
9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and 9. Lock down the permissions on the json file downloaded from step 1 so only oauth2-proxy is able to read the file and
set the path to the file in the `google-service-account-json` flag. set the path to the file in the `google-service-account-json` flag.
10. Restart oauth2-proxy. 10. Restart oauth2-proxy.