Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The instruction for creating aws-credential-process.json is not described anyware #8

Closed
masaruyokoi opened this issue Dec 20, 2023 · 2 comments · Fixed by #9
Closed
Assignees
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@masaruyokoi
Copy link

Hello.

I start to use the command aws-credential-process. I have searched carefully, but nowhere is there a description of how to create a configuration file aws-credential-process.json .

I read following docs :

I will now read the source code and find out how to write the settings in JSON.

@masaruyokoi
Copy link
Author

I understand as following:

{
 "clientId" : "XXXX (copy the value of `clientid` in ksm ini file)",
 "privateKey" : "XXXX (copy the value of `privatekey` in ksm ini file)",
 "appKey": "XXXX (copy the value of `appkey` in ksm ini file)",
 "hostname" : "keepersecurity.com", // depend on the region
 "appOwnerPublicKey" : "XXXX (copy the value of `appownerpublickey` in ksm ini file)",
 "serverPublicKeyId" : "XXXX (copy the value of `serverpublickeyid` in ksm ini file)"
}

I think the values for each config items are same as KSM python implements.

From the user's point of view, it is easier that the secret-manager-go read INI file generated by the ksm command.

@EndlessTrax
Copy link

Thanks for the issue, @masaruyokoi.

The easiest way to get the json is from the UI. Here's the official documentation link showing you how - https://docs.keeper.io/secrets-manager/secrets-manager/about/secrets-manager-configuration#creating-a-secrets-manager-configuration

I will make sure to add this to the README.md soon. Thanks for the spot.

@EndlessTrax EndlessTrax added documentation Improvements or additions to documentation question Further information is requested labels Dec 20, 2023
@EndlessTrax EndlessTrax self-assigned this Dec 20, 2023
EndlessTrax pushed a commit that referenced this issue Dec 21, 2023
* Add missing instructions for getting a JSON configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
2 participants