Skip to main content

Randomly Generating User Passwords Using Ansible

First, i would like to note that i have recently started using Ansible for configuration management. One of the things i need in my server environment is to implement a user password changing policy. Since the targets are numerous, i have to use randomly generated passwords for each host. Because passwords are sensitive, they should be generated in the encrypted form. Ansible documentation recommends using python passlib library and SHA512 hashing here.

With the following function passwords can be randomly generated in the form of strings that are 8 characters long and contain uppercase ascii characters, lowercase ascii characters and digits.

My aim is to create one playbook template for each host from the ansible hosts. On my own way getting ansible hosts can be achieved like this:

# ansible all -m ping |grep success |awk '{print $1}' |sort > server_list

And playbook templates can be created reading server_list file line by line (take note the randomly generated passwords):
That's it. Playbook templates can be run one by one:

# ansible-playbook <target_host>.yml

Or in a for loop:

# for yaml in $(ls *.yml); do ansible-playbook $yaml; done

Comments

Popular posts from this blog

Find and replace with sed command in Linux

Find and replace feature is always handy. It can turn into a torture when it comes to change or delete a simple constant string in a text file. There is a handy tool in linux for doing these kind of tihngs. Actually sed is not a text editor but it is used outside of the text file to make changes.

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector.
Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true) and combines them with the previous line that starts with a date pattern.

server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n
Logstash filter: