[
https://issues.apache.org/jira/browse/GUACAMOLE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Muehlner updated GUACAMOLE-1643:
--------------------------------------
Description:
In Keeper Secrets Manager, the usual process for generating the base64-encoded
JSON configuration blob is to use a separate application called Keeper
Commander to read the one-time token that the webapp spits out, which will
convert it to a base64 config blob.
That base64 config blob can then be copy-pasted into the connection group edit
screen.
However, we should be able to use the KSM API to directly accept the one-time
token in guacamole, validate it, and transparently transform it to a base64
config blob to be stored in the connection group parameters.
This is a follow-on for GUACAMOLE-1629.
was:
In Keeper Secrets Manager, the usual process for generating the base64-encoded
JSON configuration blob is to use a separate application called Keeper
Commander to read the one-time token that the webapp spits out, which will
convert it to a base64 config blob.
That base64 config blob can then be copy-pasted into the connection group edit
screen.
However, we should be able to use the KSM API to directly accept the one-time
token in guacamole, validate it, and transparently transform it to a base64
config blob to be stored in the connection group parameters.
> Allow use of KSM one-time tokens in guacamole-vault-ksm extension
> -----------------------------------------------------------------
>
> Key: GUACAMOLE-1643
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1643
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-vault
> Reporter: James Muehlner
> Priority: Minor
>
> In Keeper Secrets Manager, the usual process for generating the
> base64-encoded JSON configuration blob is to use a separate application
> called Keeper Commander to read the one-time token that the webapp spits out,
> which will convert it to a base64 config blob.
> That base64 config blob can then be copy-pasted into the connection group
> edit screen.
> However, we should be able to use the KSM API to directly accept the one-time
> token in guacamole, validate it, and transparently transform it to a base64
> config blob to be stored in the connection group parameters.
> This is a follow-on for GUACAMOLE-1629.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
