conjur
conjur copied to clipboard
CyberArk Conjur automatically secures secrets used by privileged users and machine identities
Before the OSS release we decided to focus on removing the possum references that a non-contributor would encounter (so basically anything that shows up in the README). There are quite...
Do NOT create the !:webservice:accounts resource or the !:!:root role automatically (these can be added via policy if needed) This happens in three places: the rake task that handles `conjurctl...
## Is your feature request related to a problem? Please describe. At current, most Conjur authenticators require end users to load some boilerplate policy to set up the authenticator for...
Both `conjurctl account create` and `conjurctl server` accept the switch `--password-from-stdin`. Please add tests that address the scenario that no STDIN is provided but the user provides this option. The...
Make client cert path configurable, either through policy or as a startup parameter. At the moment client cert path is hard coded as /etc/conjur/ssl. This configuration enforces to create a...
## Is your feature request related to a problem? Please describe. I want to use conjur with a postgres forcing `ssl_mode=verify-full` and with custom SSL cert/key and CA for the...
This is a DRAFT ## Feature Overview **As a** Conjur operator **I'd like to** know which authenticators are configured correctly **So that** I can complete the configuration properly if it's...
## Is your feature request related to a problem? Please describe. At current, if **any** secret in the list of secrets I send in a batch secrets retrieval request doesn't...
The batch secret endpoint has a bug where the comma-delimited variable_ids parameter can not correctly include resource IDs that contain commas. This is because Rails automatically unescapes URI-encoded values before...
## Is your feature request related to a problem? Please describe. ### Related User Stories - As a CyberArk developer of the simplified authentication client configuration (documented in Issue #2045),...