-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🚑️ (src/db_redis): fix empty request check (#30)
Fixed a wrong if statement in `get_request_data()`: `request_data[key]` could be `None` (because it's a string Key) or `set()` (because it's a set Key), respectively generated by `__get_key()` and `__get_skey()`. Need to check that req. data is not None and then is not an empty set. Added ldapsync support and updated UI ## Commits * 🚑️ (src/db_redis): fix emty request check Fixed a wrong if statement in `get_request_data()`: `request_data[key]` could be `None` (because it's a string Key) or `set()` (because it's a set Key), respectively generated by `__get_key()` and `__get_skey`. Need to check that req. data is not None and then is not an empty set. * 🚑 (src/routes): fix `KeyError` for new requests * 🔥 (src/): remove `ADMIN_USERS` Removed old `ADMIN_USERS` config from code. * 📝 (README): remove `ADMIN_USERS` * ✨ (src/db_redis): update groups when updating request When a requests is approved (passing from `pending` to `approved`), `groups` key are set by adding `users`. * ✨ (src/): add user infos Added functions to get and use redis userinfos keys. * 🐛 (src/db_redis): fix wrong var name * 🐛 (src/db_redis): fix missing string in logging * 💄 (src/templates/users/admin): add full user's name * 🐛 (src/routes): fix wrong argument * 🐛 (src/db_redis): fix wrong redis key format * 💄 (src/): add user's name in admin view * ✨ (src/): add notify ldapsync function * 🐛 (src/db_redis): add protocol to ldap notify * 💄 (src/templates/users/user): update user's name
- Loading branch information
Showing
7 changed files
with
60 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,15 +25,13 @@ VAULT_CLIENT_SECRET= | |
VAULT_API_BASE_URL= | ||
VAULT_CONF_URL= | ||
SECRET_KEY= | ||
ADMIN_USERS= | ||
``` | ||
|
||
> [!NOTE] | ||
> - `VAULT_API_BASE_URL` should be similar to `<ip>/v1/`. | ||
> - `VAULT_CONF_URL` should be similar to `<ip>/v1/identity/oidc/provider/<provider>/.well-known/openid-configuration`. The `<provider>` string should be `default`. | ||
> - **DON'T FORGET THE PROTOCOL (`http://` or `https://`) BEFORE THE `<ip>` STRING !!** | ||
> - `SECRET_KEY` should be invented (not provided by Voult). | ||
> - `ADMIN_USERS` must be a list of users id. Something like this `ADMIN_USERS='["[email protected]", "[email protected]", "[email protected]"]'`. | ||
> - Replace email with usernames or whatever you want. Be careful with `'` and `"`, these must be used exactly as in the example. | ||
One example of a configuration is shown below: | ||
|
@@ -44,7 +42,6 @@ VAULT_CLIENT_SECRET=hvo_secret_TcKGRPh3sjC1WE4PrS2GV3XYpY2AkL0FEgYWRNQUPw7rLTYSS | |
VAULT_API_BASE_URL=http://localhost:8200/v1/ | ||
VAULT_CONF_URL=http://127.0.0.1:8200/v1/identity/oidc/provider/default/.well-known/openid-configuration | ||
SECRET_KEY=!secret | ||
ADMIN_USERS='["[email protected]", "[email protected]", "[email protected]"]' | ||
``` | ||
|
||
## Run | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters