Open tiwarishrijan opened 1 month ago
idimov-keeper
commented
1 month ago 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
commented
1 month ago 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
commented
1 month ago 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?
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 ?