Setting up splunk admin could be easier #226
Comments
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jun 28, 2019
This commit introduces a new set of parameters that can be used instead of the previous "manage_password" parameter to set the initial admin password through the documented user-seed.conf method. The old method still exists but now logs a message indicating that it is no longer the preferred method. This is being done to align the module with Splunk's documentation, prevent Puppet from causing a correctional change on each run, and make it possible to reset the admin password from the Splunk console when desired Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jun 28, 2019
This commit introduces a new set of parameters that can be used instead of the previous "manage_password" parameter to set the initial admin password through the documented user-seed.conf method. The old method still exists but now logs a message indicating that it is no longer the preferred method. This is being done to align the module with Splunk's documentation, prevent Puppet from causing a correctional change on each run, and make it possible to reset the admin password from the Splunk console when desired Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jun 28, 2019
This commit introduces a new set of parameters that can be used instead of the previous "manage_password" parameter to set the initial admin password through the documented user-seed.conf method. The old method still exists but now logs a message indicating that it is no longer the preferred method. This is being done to align the module with Splunk's documentation, prevent Puppet from causing a correctional change on each run, and make it possible to reset the admin password from the Splunk console when desired Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 12, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 12, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 12, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 12, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 12, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 13, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 17, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 17, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 17, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
ody
added a commit
to ody/puppet-splunk
that referenced
this issue
Jul 17, 2019
This commit introduces a new set of parameters and classes that
are used instead of the previous implementation of the
"manage_password" parameter to set the initial admin password
through the documented user-seed.conf method. The old method
still exists but now logs a message indicating that it is no
longer the preferred method.
This is being done to align the module with Splunk's
documentation, prevent Puppet from causing a correctional change
on each run, and make it possible to reset the admin password
from the Splunk console when desired.
The new seed method was implemented in a class separate from
Class[splunk::{enterprise,forwarder}::config] to enable it to be
easily used external from Puppet, specifically with a Bolt Plan
in mind so people can reset the seeded admin password easily
without the need to temporarily change infrastructure data sets.
The old direct management method was migrated to the same method
just for consistency.
Fixes voxpupuli#226
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the refactored master branch, I was getting “No users exist. Please set up a user.” in the Splunk web console after installation (using the
splunk::enterpriseclass).To solve this, I had to add the
manage_password => trueandpassword_content => <valid content>attributes.It works with a correct password_content value but that is difficult to generate if you don’t have an existing server to glen the /opt/splunk/etc/passwd file from...
It would probably be better if one of the methods documented here were used to seed a default password, so at least the admin account gets setup.
The
user-seed.confmethod didn’t work for me however. The create admin credentials via REST method did work.The text was updated successfully, but these errors were encountered: