Michael Jumper
c5ae027225
GUACAMOLE-641: Add user- and gateway-specific tokens.
2022-01-22 22:25:04 -08:00
Michael Jumper
b655866057
GUACAMOLE-641: Consider existing tokens when injecting tokens from vault.
2022-01-22 22:25:04 -08:00
Michael Jumper
d2f5596015
GUACAMOLE-641: Automatically provide KEEPER_SERVER_* tokens based on connection parameters.
2022-01-22 22:25:04 -08:00
Michael Jumper
30f24de808
GUACAMOLE-641: Allow vault implementations to automatically provide tokens based on connection parameters (without YAML mapping).
2022-01-22 22:25:04 -08:00
Michael Jumper
d0bd4b52d6
GUACAMOLE-641: Add general service for retrieving data from Keeper records.
2022-01-22 22:25:04 -08:00
Michael Jumper
d0043e34dd
GUACAMOLE-641: Allow token mapping file to not exist.
...
Some tokens may be standardized or specific to the implementation, and
may not need to be defined in YAML.
2022-01-22 22:25:04 -08:00
Michael Jumper
8bedbe746c
GUACAMOLE-641: Add initial draft implementation of KSM vault support for Guacamole.
2022-01-22 22:25:04 -08:00
Michael Jumper
786430612e
GUACAMOLE-641: Canonicalize individual, tokenized components of secret names rather than the whole name.
...
In the event that a secret name is structured, such as the URL-like
notation used by Keeper Secrets Manager, canonicalizing/encoding the
entire name could result in the name itself becoming invalid. Only the
portions that come from tokens should be canonicalized.
2022-01-22 22:25:04 -08:00
Michael Jumper
16cb9ed69b
GUACAMOLE-641: Expand CONNECTION_USERNAME and CONNECTION_HOSTNAME tokens only if corresponding parameters are non-empty.
2022-01-22 22:25:04 -08:00
Michael Jumper
4d3b2a9435
GUACAMOLE-641: Obtain connection hostname and/or username for vault tokens via privileged access, if possible.
2022-01-22 22:25:04 -08:00
Michael Jumper
5aba0cd09d
GUACAMOLE-641: Read token/secret mapping from YAML instead of JSON.
2022-01-22 22:25:04 -08:00
Michael Jumper
b57578ad8e
GUACAMOLE-641: Rename vault-specific username token to "USERNAME" to avoid confusion with "GUAC_USERNAME".
...
The "GUAC_USERNAME" token provided by the webapp is based off the
username provided by the user when they authenticated. The username
token provided by the vault extensions uses the username stored with
the user's corresponding object, which may not be the same.
2022-01-22 22:25:04 -08:00
Michael Jumper
f99b3a3213
GUACAMOLE-641: Rename guacamole-auth-vault to guacamole-vault (does not provide auth).
2022-01-22 22:25:04 -08:00
