fortinet.fortimanager.fmgr_user_device – Configure devices.

Note

This plugin is part of the fortinet.fortimanager collection (version 2.1.4).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core. To check whether it is installed, run ansible-galaxy collection list.

To install it, use: ansible-galaxy collection install fortinet.fortimanager.

To use it in a playbook, specify: fortinet.fortimanager.fmgr_user_device.

New in version 2.10: of fortinet.fortimanager

Synopsis

  • This module is able to configure a FortiManager device.

  • Examples include all parameters and values which need to be adjusted to data sources before usage.

Parameters

Parameter

Comments

adom

string / required

the parameter (adom) in requested url

bypass_validation

boolean

only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters

Choices:

  • no ← (default)

  • yes

enable_log

boolean

Enable/Disable logging for task

Choices:

  • no ← (default)

  • yes

proposed_method

string

The overridden method for the underlying Json RPC request

Choices:

  • update

  • set

  • add

rc_failed

list / elements=string

the rc codes list with which the conditions to fail will be overriden

rc_succeeded

list / elements=string

the rc codes list with which the conditions to succeed will be overriden

state

string / required

the directive to create, update or delete an object

Choices:

  • present

  • absent

user_device

dictionary

the top level parameters set

alias

string

Device alias.

avatar

string

Image file for avatar (maximum 4K base64 encoded).

category

string

Device category.

Choices:

  • none

  • android-device

  • blackberry-device

  • fortinet-device

  • ios-device

  • windows-device

  • amazon-device

comment

string

Comment.

dynamic_mapping

list / elements=string

Dynamic_Mapping.

_scope

list / elements=string

_Scope.

name

string

Name.

vdom

string

Vdom.

avatar

string

Image file for avatar (maximum 4K base64 encoded).

category

string

Family.

Choices:

  • none

  • android-device

  • blackberry-device

  • fortinet-device

  • ios-device

  • windows-device

  • amazon-device

comment

string

Comment.

family

string

Family.

hardware-vendor

string

Hardware-Vendor.

hardware-version

string

Hardware-Version.

mac

string

Device MAC address.

master-device

string

Master device (optional).

os

string

Os.

software-version

string

Software-Version.

tags

string

Tags.

type

string

Type.

Choices:

  • ipad

  • iphone

  • gaming-console

  • blackberry-phone

  • blackberry-playbook

  • linux-pc

  • mac

  • windows-pc

  • android-phone

  • android-tablet

  • media-streaming

  • windows-phone

  • fortinet-device

  • ip-phone

  • router-nat-device

  • other-network-device

  • windows-tablet

  • printer

  • forticam

  • fortifone

  • unknown

user

string

User name.

mac

string

Device MAC address(es).

master-device

string

Master device (optional).

tagging

list / elements=string

Tagging.

category

string

Tag category.

name

string

Tagging entry name.

tags

string

Tags.

type

string

Device type.

Choices:

  • ipad

  • iphone

  • gaming-console

  • blackberry-phone

  • blackberry-playbook

  • linux-pc

  • mac

  • windows-pc

  • android-phone

  • android-tablet

  • media-streaming

  • windows-phone

  • fortinet-device

  • ip-phone

  • router-nat-device

  • other-network-device

  • windows-tablet

  • printer

  • forticam

  • fortifone

  • unknown

user

string

User name.

workspace_locking_adom

string

the adom to lock for FortiManager running in workspace mode, the value can be global and others including root

workspace_locking_timeout

integer

the maximum time in seconds to wait for other user to release the workspace lock

Default: 300

Notes

Note

  • Running in workspace locking mode is supported in this FortiManager module, the top level parameters workspace_locking_adom and workspace_locking_timeout help do the work.

  • To create or update an object, use state present directive.

  • To delete an object, use state absent directive.

  • Normally, running one module can fail when a non-zero rc is returned. you can also override the conditions to fail or succeed with parameters rc_failed and rc_succeeded

Examples

- name: gathering fortimanager facts
  hosts: fortimanager00
  gather_facts: no
  connection: httpapi
  collections:
    - fortinet.fortimanager
  vars:
    ansible_httpapi_use_ssl: True
    ansible_httpapi_validate_certs: False
    ansible_httpapi_port: 443
  tasks:
   - name: retrieve all the devices
     fmgr_fact:
       facts:
           selector: 'user_device'
           params:
               adom: 'ansible'
               device: ''

- hosts: fortimanager00
  collections:
    - fortinet.fortimanager
  connection: httpapi
  vars:
     ansible_httpapi_use_ssl: True
     ansible_httpapi_validate_certs: False
     ansible_httpapi_port: 443
  tasks:
   - name: Configure devices.
     fmgr_user_device:
        bypass_validation: False
        adom: ansible
        state: present
        user_device:
           alias: ansible-test-device
           category: android-device #<value in [none, android-device, blackberry-device, ...]>
           comment: ansible-comment
           mac: '00:11:22:33:44:55'
           type: iphone #<value in [ipad, iphone, gaming-console, ...]>

Return Values

Common return values are documented here, the following are the fields unique to this module:

Key

Description

request_url

string

The full url requested

Returned: always

Sample: “/sys/login/user”

response_code

integer

The status of api request

Returned: always

Sample: 0

response_message

string

The descriptive message of the api response

Returned: always

Sample: “OK.”

Authors

  • Link Zheng (@chillancezen)

  • Jie Xue (@JieX19)

  • Frank Shen (@fshen01)

  • Hongbin Lu (@fgtdev-hblu)