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

Missing Documentation or Functionality #629

Open
tiwarishrijan opened this issue Jul 30, 2024 · 4 comments
Open

Missing Documentation or Functionality #629

tiwarishrijan opened this issue Jul 30, 2024 · 4 comments

Comments

@tiwarishrijan
Copy link

I am unable to find any method where i can retrieve meta information about my secret in regards to who created it, when it was last modified etc.
Do we have this functionality already in SDK or any alternative method i can use to retrieve ?

@idimov-keeper
Copy link
Collaborator

For that you should use Commander Python or .NET SDKs, not Secrets Manager which was mainly designed to be a light weight SDK to work with record data only.

https://docs.keeper.io/secrets-manager/commander-cli/overview

@tiwarishrijan
Copy link
Author

tiwarishrijan commented Aug 6, 2024

I maybe wrong but commander CLI need user login capability? Is there is a better way ? I will assume secret manager should expose its metadata as well so that i can use single construct.

Another problem with commander is the permission :
Grant Commander SDK permissions to access Keeper by navigating to Admin Console -> Admin -> Roles -> [Select User's Role] -> Enforcement Policies -> Platform Restrictions -> Click on 'Enable' check box next to Commander SDK. Also note that if user has more than two roles assigned then the most restrictive policy from all the roles will be applied.

@maksimu
Copy link
Collaborator

maksimu commented Aug 6, 2024

I maybe wrong but commander CLI need user login capability?

In Commander you can configure Persistent login and use it in your automation scripts.

will assume secret manager should expose its metadata as well so that i can use single construct.

At this time we have no plans to expose any metadata via KSM, but I'll note that for our product team to consider it.

Another problem with commander is the permission :
Grant Commander SDK permissions to access Keeper by navigating to Admin Console -> Admin -> Roles -> [Select User's Role] -> Enforcement Policies -> Platform Restrictions -> Click on 'Enable' check box next to Commander SDK. Also note that if user has more than two roles assigned then the most restrictive policy from all the roles will be applied.

Can you elaborate why that is a problem?

@flybyray
Copy link

In Commander you can configure Persistent login and use it in your automation scripts.

Please put a bit more context to it, so that users understand the difference of those products.
I would like to see an official statement about the API endpoint performance KSM vs Commander.
I tested to replace KSM with Commander persistent login. For me it seems like the Commander API endpoint is throttled really bad. Maybe to force better sales for KSM :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants