You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@ This are the software you need to have in order to run PassWeaver API:
27
27
These are the features this API support, in random order:
28
28
29
29
- Cloud KMS integration (currently, only Google Cloud KMS)
30
+
- Login via Google OAuth2 token validation
30
31
- API keys, with IP whitelist and day of week/time whitelist
31
32
- Personal folders for each user
32
33
- Favorite items
@@ -143,6 +144,14 @@ PassWeaver API users can be authenticated via these methods:
143
144
- Local: the user password hash is stored locally in the database
144
145
- LDAP: authenticate against a LDAP/Active Directory server
145
146
- API key: authenticate only via an existing API key
147
+
- Google OAuth2 token validation: see below
148
+
149
+
### Google OAuth2 token validation
150
+
151
+
You can integrate your frontend with Google OAuth2 (PassWeaver GUI supports is), and once you obtain a valid token PassWeaver API can validate it and obtain the informations to log you in:
152
+
it will look for an existing user with the email obtained from the token.
153
+
154
+
In order to enable Google OAuth2, you have to set auth.google_oauth2 in the configuration, and export GOOGLE_CLIENT_ID of your Google API Key in your environment.
146
155
147
156
## Authorization
148
157
@@ -434,6 +443,10 @@ Copy `config-skel.json` to `config.json` and adjust the options (all options are
434
443
-`enable_metrics`: true or false, enables Prometheus-formatted metrics
435
444
-`generated_password_length`: default length of random generated password (default is 15)
436
445
-`cache-control`: Cache-Control header to be sent along GET/HEAD responses
446
+
-`auth`:
447
+
-`google_oauth2`:
448
+
-`enabled`: if true, the login endpoint will accept the token for authenticating with Google OAuth2 token. Note that you have to set "GOOGLE_CLIENT_ID" in your environment
0 commit comments