cisco.ise.bind_signed_certificate module – Resource module for Bind Signed Certificate
Note
This module is part of the cisco.ise collection (version 2.9.5).
To install it, use: ansible-galaxy collection install cisco.ise
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.ise.bind_signed_certificate
.
New in cisco.ise 1.0.0
Synopsis
Manage operation create of the resource Bind Signed Certificate.
Bind CA Signed Certificate.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
ciscoisesdk >= 2.2.3
python >= 3.5
Parameters
Parameter |
Comments |
---|---|
Use certificate to authenticate the Cisco ISE Admin Portal. Choices: |
|
Allow import of certificates with validity greater than 398 days (required). Choices: |
|
Allow out of date certificates (required). Choices: |
|
Allow Replacement of certificates (required). Choices: |
|
Allow Replacement of Portal Group Tag (required). Choices: |
|
Signed certificate data (required). |
|
Use certificate for EAP protocols that use SSL/TLS tunneling. Choices: |
|
Name of Host whose CSR ID has been provided (required). |
|
ID of the generated CSR (required). |
|
Use certificate for the Cisco ISE Messaging Service. Choices: |
|
Flag for Identity Services Engine SDK to enable debugging. Choices: |
|
The Identity Services Engine hostname. |
|
The Identity Services Engine password to authenticate. |
|
Timeout (in seconds) for RESTful HTTP requests. Default: :ansible-option-default:`60` |
|
The Identity Services Engine username to authenticate. |
|
Flag that informs the SDK whether to use the Identity Services Engine’s API Gateway to send requests. If it is true, it uses the ISE’s API Gateway and sends requests to https://{{ise_hostname}}. If it is false, it sends the requests to https://{{ise_hostname}}:{{port}}, where the port value depends on the Service used (ERS, Mnt, UI, PxGrid). Choices: |
|
Flag that informs the SDK whether we send the CSRF token to ISE’s ERS APIs. If it is True, the SDK assumes that your ISE CSRF Check is enabled. If it is True, it assumes you need the SDK to manage the CSRF token automatically for you. Choices: |
|
Flag to enable or disable SSL certificate verification. Choices: |
|
Informs the SDK which version of Identity Services Engine to use. |
|
Flag for Identity Services Engine SDK to enable automatic rate-limit handling. Choices: |
|
Friendly Name of the certificate. |
|
Set Group tag. |
|
Use certificate for the pxGrid Controller. Choices: |
|
Use certificate for the RADSec server. Choices: |
|
Use certificate for SAML Signing. Choices: |
|
Validate Certificate Extensions. Choices: |
Notes
Note
SDK Method used are certificates.Certificates.bind_csr,
Paths used are post /api/v1/certs/signed-certificate/bind,
Does not support
check_mode
The plugin runs on the control node and does not use any ansible connection plugins, but instead the embedded connection manager from Cisco ISE SDK
The parameters starting with ise_ are used by the Cisco ISE Python SDK to establish the connection
See Also
See also
- Cisco ISE documentation for Certificates
Complete reference of the Certificates API.
Examples
- name: Create
cisco.ise.bind_signed_certificate:
ise_hostname: "{{ise_hostname}}"
ise_username: "{{ise_username}}"
ise_password: "{{ise_password}}"
ise_verify: "{{ise_verify}}"
admin: true
allowExtendedValidity: true
allowOutOfDateCert: true
allowReplacementOfCertificates: true
allowReplacementOfPortalGroupTag: true
data: string
eap: true
hostName: string
id: string
ims: true
name: string
portal: true
portalGroupTag: string
pxgrid: true
radius: true
saml: true
validateCertificateExtensions: true
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
A dictionary or list with the response returned by the Cisco ISE Python SDK Returned: always |