Skip to content

Simplify Initialization of Keeper Secrets Manager Integration #2048

@maksimu

Description

@maksimu

Describe the solution you'd like
Simplify the way Keeper Secrets Manager configuration is initialized, namely use base64 configuration as opposed to use individual parts from the JSON file

What is the added value?
Simplicity of configuring access

Observations (Constraints, Context, etc):

As it is stated in Keeper documentation page:

Most Secrets Manager integrations use a base64 string ...

In Go SDK this is how it is set:

options := &ksm.ClientOptions{
	Config: ksm.NewMemoryKeyValueStorage("LONG BASE64 STRING")
}

It looks like all is needed is to simplify KeeperSecurityProvider to just contain base64 string and then change what getKeeperSecurityConfig returns.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions