-
Notifications
You must be signed in to change notification settings - Fork 3
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
Module supports using the Deferred Type to execute lookups on the remote node #13
Comments
|
Adding note from #20 To follow Puppet 6 best practices for secrets retrieval, we will update the Puppet integration to use deferred actions by default.
|
|
Additional notes from the original definition of #20 With the arrival of Puppet 6's deferred data types, we can move credential retrieval off the Puppet master and onto the node being configured. Deferred data types reduce the security challenges by eliminating the Puppet Master as a conduit for credential delivery. This effort will address the following areas:
ReferencesRelated issues
|
|
There is an initial implementation of this in #179. This issue will remain open until a more complete implementation is done. |
|
Per the new code that is now on the main brach, method signature has to change to accommodate the New signatures:
$dbpass = Sensitive(Deferred(conjur::secret, ['production/postgres/password']))
$sslcert = @("EOT")
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
|-EOT
$dbpass = Sensitive(Deferred(conjur::secret, ['production/postgres/password',
"https://my.conjur.org",
"myaccount",
"host/myhost",
Sensitive("2z9mndg1950gcx1mcrs6w18bwnp028dqkmc34vj8gh2p500ny1qk8n"),
$sslcert
]))The longer signature may also change again depending on if #184 gets implemented. |
|
Released with v3.0.0rc3. Closing. |
As a Puppet operator, I want to be able to leverage Puppet's new Deferred Type, so that I can use the remote node's identity to retrieve secrets from Conjur, without having those secrets transferred to the master.
GIVEN a Puppet master and an un-configured node which is enrolled in Conjur and have permission to access a credential
WHEN the module is run against the node
THEN credential are placed on the node
AND that credential does not flow through the master
Developer Notes
Overview and example of how this can be done in the upcoming Puppet 6 release: https://gist.github.com/turbodog/06d3fecef403bfefd9c8174ede4d9174
The text was updated successfully, but these errors were encountered: