You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iIn puppet it looks like even getting the master server cert is fragile to the max - we assume that if the indirector is not :compiler we use methods only available in :rest indirector even though there’s like 16 different types.
I think we may need to figure out different asymmetric key data to encrypt the token with between agent and master
def standalone?
# HACK is there a better way to detect if this is puppet apply?
Puppet[:catalog_terminus] == :compiler
end
begin
...
if standalone?
config['token'] = token
else
config['encrypted_token'] = encrypt_for_master token
end
end
def puppet_certificate
@puppet_certificate ||= begin
itc = Puppet::Resource::Catalog.indirection.terminus.class
get_ssl_cert itc.server, itc.port,
Puppet::SSL::Validator.default_validator.ssl_configuration.ca_chain_file
end
end
Here, itc.server and itc.port are only available to REST indirector
On Puppet 6, the Conjur module reports the error:
This comes from
conjur-puppet/lib/facter/conjur.rb
Line 75 in 353c3e2
This instance method existed in Puppet 5 but was removed in Puppet 6.
The text was updated successfully, but these errors were encountered: