[
https://issues.apache.org/jira/browse/GUACAMOLE-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Jumper closed GUACAMOLE-2030.
----------------------------------
Fix Version/s: 1.6.1
Resolution: Fixed
> 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
> Fix For: 1.6.1
>
>
> 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}
> There is a lack of KSM error documentation and there are no exception
> subclasses so we have to try per-user KSM config in case of any failures.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
