Change root password on existing host

Support
1

Is it possible to change the root password on an existing host through the
Foreman web gui (under Edit host)? I tried setting it to a plaintext value
as well as a encrypted string using grub-crypt on CentOS 6.4, but no luck.
I figured the root pass field was only used when provisioning, but thought
I'd ask.

I'm running Foreman 1.1 on CentOS 6.4 with Puppet 3.1.1.

2

Foreman doesn't make direct changes to hosts - that's Puppet's job. We used
to provide the encrypted value of the password as a value in the ENC data,
but that was removed recently as it was rarely used and could be construed
as a security leak.

As of right now, you best bet is to do this through puppet. If it's still
important to have the data in Foreman (and you don't mind the implications)
you could also use a Host/Host Group parameter.

HTH,
Greg

··· On 18 June 2013 20:47, Jason Ashby wrote:

Is it possible to change the root password on an existing host through the
Foreman web gui (under Edit host)? I tried setting it to a plaintext value
as well as a encrypted string using grub-crypt on CentOS 6.4, but no luck.
I figured the root pass field was only used when provisioning, but thought
I’d ask.

I’m running Foreman 1.1 on CentOS 6.4 with Puppet 3.1.1

3

Thanks Greg, that makes sense. I'll keep this quote in mind:

Foreman doesn't make direct changes to hosts - that's Puppet's job.

··· On Tuesday, June 18, 2013 5:48:36 PM UTC-4, Greg Sutcliffe wrote: > > On 18 June 2013 20:47, Jason Ashby <jas...@gmail.com > wrote: > >> Is it possible to change the root password on an existing host through >> the Foreman web gui (under Edit host)? I tried setting it to a plaintext >> value as well as a encrypted string using grub-crypt on CentOS 6.4, but no >> luck. I figured the root pass field was only used when provisioning, but >> thought I'd ask. >> >> I'm running Foreman 1.1 on CentOS 6.4 with Puppet 3.1.1 > > > Foreman doesn't make direct changes to hosts - that's Puppet's job. We > used to provide the encrypted value of the password as a value in the ENC > data, but that was removed recently as it was rarely used and could be > construed as a security leak. > > As of right now, you best bet is to do this through puppet. If it's still > important to have the data in Foreman (and you don't mind the implications) > you could also use a Host/Host Group parameter. > > HTH, > Greg > >
4

at the end of the provisioning process, or being able to 'kick' a node via
Puppetrun/Mcollective) but in general, it's true :wink:

Greg

··· On 19 June 2013 14:46, Jason Ashby wrote:

Thanks Greg, that makes sense. I’ll keep this quote in mind:

Foreman doesn’t make direct changes to hosts - that’s Puppet’s job.

There are, of course, exceptions to the rule (such as the Finish templates