I would do it the other way around - set up a YAML file with the usernames and passwords on the Ansible controller
and change the passwords based on that. The YAML file should be encrypted with Ansible vault for security.
>
> On Friday, 30 August 2019 02:33:20 UTC-4, Dick Visser wrote:
>
> It depends on what your vpn box looks like and how easy it is to change passwords on it.
> You can loop over the users changing their password to a random value and then writing those to files named after
> the user name.
> This is just one way of doing it- there are probably more.
>
> But whatever you come up with, as an affected user I wouldn’t be very happy if someone else sets a password for me
> and then copies that around in plain text files.
> You can try to secure this but ultimately it’s best to offer a secure way for users to do this themselves. Or have
> the vpn box authenticate users to some existing directory (both of which might not be possible, depending on your
> situation).
>
> Dick
>
>
> On Fri, 30 Aug 2019 at 08:20, Andrew Morgan <
alonso...@gmail.com <javascript:>> wrote:
>
> Hello All,
>
> I have a task to change all the password on a vpnbox and then give the user their password. I have been
> researching and think I found a way to do it, but I am not sure how I then get the password to output to a file
> to then give the user. Is there a way I can go about doing that? After assigning a password, out the password
> that was assigned and the user's name to a file.
>
> Thank you
>
> --
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ansible...@googlegroups.com
Debian and Sympa administration. Provisioning with Ansible.