[
https://issues.apache.org/jira/browse/GUACAMOLE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugen Hartmann updated GUACAMOLE-2030:
--------------------------------------
Description:
KSM static token mapping does not work with a per user KSM config. Also, the
log contains the following messages:
{noformat}
WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/login" is not
valid Keeper notation. Please check the documentation at
https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
for valid formatting.
WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/password" is not
valid Keeper notation. Please check the documentation at
https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
for valid formatting.
{noformat}
This happens because the *record not found" error comes as a plain Java
exception but the current code considers only pure parsing failures can throw
the exceptions.
{noformat}
java.lang.Exception: Record 'XXX' not found at
com.keepersecurity.secretsManager.core.Notation.getValue(Notation.kt:23)
{noformat}
was:
KSM static token mapping does not work with a per user KSM config. Also, there
are the log contains the following messages:
{noformat}
WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/login" is not
valid Keeper notation. Please check the documentation at
https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
for valid formatting.
WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/password" is not
valid Keeper notation. Please check the documentation at
https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
for valid formatting.
{noformat}
This happens because the *record not found" error comes as a plain Java
exception but the current code considers only pure parsing failures can throw
the exceptions.
{noformat}
java.lang.Exception: Record 'XXX' not found at
com.keepersecurity.secretsManager.core.Notation.getValue(Notation.kt:23)
{noformat}
> KSM static token mapping does not work with a per user config
> -------------------------------------------------------------
>
> Key: GUACAMOLE-2030
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2030
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.5.5
> Reporter: Eugen Hartmann
> Priority: Major
>
> KSM static token mapping does not work with a per user KSM config. Also, the
> log contains the following messages:
> {noformat}
> WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/login" is not
> valid Keeper notation. Please check the documentation at
> https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
> for valid formatting.
> WARN o.a.g.vault.ksm.secret.KsmClient - "keeper://XXX/field/password" is not
> valid Keeper notation. Please check the documentation at
> https://docs.keeper.io/secrets-manager/secrets-manager/about/keeper-notation
> for valid formatting.
> {noformat}
> This happens because the *record not found" error comes as a plain Java
> exception but the current code considers only pure parsing failures can throw
> the exceptions.
> {noformat}
> java.lang.Exception: Record 'XXX' not found at
> com.keepersecurity.secretsManager.core.Notation.getValue(Notation.kt:23)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
