cisco.nxos.nxos_user – Manage the collection of local users on Nexus devices
Note
This plugin is part of the cisco.nxos collection (version 1.4.0).
To install it use: ansible-galaxy collection install cisco.nxos.
To use it in a playbook, specify: cisco.nxos.nxos_user.
New in version 1.0.0: of cisco.nxos
Synopsis
- This module provides declarative management of the local usernames configured on Cisco Nexus devices. It allows playbooks to manage either individual usernames or the collection of usernames in the current running config. It also supports purging usernames from the configuration that are not explicitly defined.
 
Note
This module has a corresponding action plugin.
Parameters
| Parameter | Choices/Defaults | Comments | |
|---|---|---|---|
|   aggregate    list / elements=dictionary    |    The set of username objects to be configured on the remote Cisco Nexus device. The list entries can either be the username or a hash of username and properties. This argument is mutually exclusive with the   name argument.aliases: users, collection  |  ||
|   configured_password    string    |    The password to be configured on the network device. The password needs to be provided in cleartext and it will be encrypted on the device. Please note that this option is not same as   provider password. |  ||
|   name    string    |    The username to be configured on the remote Cisco Nexus device. This argument accepts a string value and is mutually exclusive with the   aggregate argument. |  ||
|   roles    list / elements=string    |    The   role argument configures the role for the username in the device running configuration. The argument accepts a string value defining the role name. This argument does not check if the role has been configured on the device.aliases: role  |  ||
|   sshkey    string    |    The   sshkey argument defines the SSH public key to configure for the username. This argument accepts a valid SSH key value. |  ||
|   state    string    |   
  |    The   state argument configures the state of the username definition as it relates to the device operational configuration. When set to present, the username(s) should be configured in the device active configuration and when set to absent the username(s) should not be in the device active configuration |  |
|   update_password    string    |   
  |    Since passwords are encrypted in the device running config, this argument will instruct the module when to change the password. When set to   always, the password will always be updated in the device and when set to on_create the password will be updated only if the username is created. |  |
|   configured_password    string    |    The password to be configured on the network device. The password needs to be provided in cleartext and it will be encrypted on the device. Please note that this option is not same as   provider password. |  ||
|   name    string    |    The username to be configured on the remote Cisco Nexus device. This argument accepts a string value and is mutually exclusive with the   aggregate argument. |  ||
|   provider    dictionary    |    Deprecated  Starting with Ansible 2.5 we recommend using   connection: network_cli.Starting with Ansible 2.6 we recommend using   connection: httpapi for NX-API.This option will be removed in a release after 2022-06-01.  For more information please see the NXOS Platform Options guide.   A dict object containing connection details.   |  ||
|   auth_pass    string    |    Specifies the password to use if required to enter privileged mode on the remote device. If authorize is false, then this argument does nothing. If the value is not specified in the task, the value of environment variable   ANSIBLE_NET_AUTH_PASS will be used instead. |  ||
|   authorize    boolean    |   
  |    Instructs the module to enter privileged mode on the remote device before sending any commands. If not specified, the device will attempt to execute all commands in non-privileged mode. If the value is not specified in the task, the value of environment variable   ANSIBLE_NET_AUTHORIZE will be used instead. |  |
|   host    string    |    Specifies the DNS host name or address for connecting to the remote device over the specified transport. The value of host is used as the destination address for the transport.   |  ||
|   password    string    |    Specifies the password to use to authenticate the connection to the remote device. This is a common argument used for either cli or nxapi transports. If the value is not specified in the task, the value of environment variable   ANSIBLE_NET_PASSWORD will be used instead. |  ||
|   port    integer    |    Specifies the port to use when building the connection to the remote device. This value applies to either cli or nxapi. The port value will default to the appropriate transport common port if none is provided in the task. (cli=22, http=80, https=443).   |  ||
|   ssh_keyfile    string    |    Specifies the SSH key to use to authenticate the connection to the remote device. This argument is only used for the cli transport. If the value is not specified in the task, the value of environment variable   ANSIBLE_NET_SSH_KEYFILE will be used instead. |  ||
|   timeout    integer    |    Specifies the timeout in seconds for communicating with the network device for either connecting or sending commands. If the timeout is exceeded before the operation is completed, the module will error. NX-API can be slow to return on long-running commands (sh mac, sh bgp, etc).   |  ||
|   transport    string    |   
  |    Configures the transport connection to use when connecting to the remote device. The transport argument supports connectivity to the device over cli (ssh) or nxapi.   |  |
|   use_proxy    boolean    |   
  |    If   no, the environment variables http_proxy and https_proxy will be ignored. |  |
|   use_ssl    boolean    |   
  |    Configures the transport to use SSL if set to   yes only when the transport=nxapi, otherwise this value is ignored. |  |
|   username    string    |    Configures the username to use to authenticate the connection to the remote device. This value is used to authenticate either the CLI login or the nxapi authentication depending on which transport is used. If the value is not specified in the task, the value of environment variable   ANSIBLE_NET_USERNAME will be used instead. |  ||
|   validate_certs    boolean    |   
  |    If   no, SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates. If the transport argument is not nxapi, this value is ignored. |  |
|   purge    boolean    |   
  |    The   purge argument instructs the module to consider the resource definition absolute. It will remove any previously configured usernames on the device with the exception of the `admin` user which cannot be deleted per nxos constraints. |  |
|   roles    list / elements=string    |    The   role argument configures the role for the username in the device running configuration. The argument accepts a string value defining the role name. This argument does not check if the role has been configured on the device.aliases: role  |  ||
|   sshkey    string    |    The   sshkey argument defines the SSH public key to configure for the username. This argument accepts a valid SSH key value. |  ||
|   state    string    |   
  |    The   state argument configures the state of the username definition as it relates to the device operational configuration. When set to present, the username(s) should be configured in the device active configuration and when set to absent the username(s) should not be in the device active configuration |  |
|   update_password    string    |   
  |    Since passwords are encrypted in the device running config, this argument will instruct the module when to change the password. When set to   always, the password will always be updated in the device and when set to on_create the password will be updated only if the username is created. |  |
Notes
Note
- For information on using CLI and NX-API see the NXOS Platform Options guide
 - For more information on using Ansible to manage network devices see the Ansible Network Guide
 - For more information on using Ansible to manage Cisco devices see the Cisco integration page.
 
Examples
- name: create a new user
  cisco.nxos.nxos_user:
    name: ansible
    sshkey: "{{ lookup('file', '~/.ssh/id_rsa.pub') }}"
    state: present
- name: remove all users except admin
  cisco.nxos.nxos_user:
    purge: yes
- name: set multiple users role
  cisco.nxos.nxos_user:
    aggregate:
    - name: netop
    - name: netend
    role: network-operator
  state: present
   Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Returned | Description | 
|---|---|---|
|   commands    list / elements=string    |  always |   The list of configuration mode commands to send to the device  Sample:  ['name ansible', 'name ansible password password']   |  
Authors
- Peter Sprygada (@privateip)
 
    © 2012–2018 Michael DeHaan
© 2018–2021 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
    https://docs.ansible.com/ansible/2.11/collections/cisco/nxos/nxos_user_module.html