Overview
Cohesity is a data protection and backup platform. It consolidates backup, recovery and long-term retention for virtual machines, databases, NAS shares and physical servers onto a scale-out cluster, replacing separate backup products and their media servers. Protection policies decide what gets backed up, how often and how long copies are kept, and the cluster reports on which jobs succeeded and which objects are protected at all.
The ReadyWorks connector talks to the Cohesity cluster’s v1 public REST API. It posts a username, password and authentication domain to the access tokens endpoint, reads the bearer token from the accessToken node in the response, and sends that token on every subsequent call. Data lands in whichever staging table each job names in the estate.
Backup coverage is one of the harder things to answer across an estate, and it is exactly the kind of question a migration or decommission wave has to answer. Pulled into the fabric and reconciled against the server and application records already there, Cohesity data shows which machines are protected, which are not, and which have a policy that no longer matches what the workload has become. That turns an assumption into a gate you can enforce before a wave moves.
The connector is declared bidirectional and both job forms are fully exposed, but no Cohesity endpoint ships. Both templates are generic REST skeletons with no endpoint set, so the endpoints have to be configured against your Cohesity API documentation.
NOTE: The authentication method is not marked as the default, even though it is the only one offered. Select it explicitly when creating the connection.
Connector Properties
Authentication Methods
One authentication method is shipped, matching the Cohesity access tokens flow.
Method 1: POST username / password / domain – return bearer token (COHESITY_452248034d)
Authentication used for Cohesity (Storage Solution)
Posts the username, password and authentication domain as a JSON body to the access tokens endpoint, reads the bearer token from the accessToken node, and attaches it as Authorization: Bearer on the data calls. All five inputs (domain, username, password, token endpoint and token node) are required, and the endpoint and node ship with working defaults for the v1 public API. The Domain value is the Cohesity authentication domain the account belongs to, which is LOCAL for a cluster-local account and the Active Directory domain name for a directory account.
Connection Configuration Fields (9)
Authentication Configuration
Headers sent on the authentication call:
Headers sent on the data calls:
Authentication request body:
cURL options:
NOTE: The Domain field uses a masked password input, so the value is hidden as you type and stored encrypted even though a domain name is not a secret. Type it carefully, because you cannot read it back to check it.
Inbound Job Fields Enabled (44)
The inbound job form carries the full generic REST field set, including pagination, the three enumeration levels and the raw JSON body.
NOTE: Several labels and tooltips carry unedited text from the shared templates. Enumaration 1 Node is misspelled and the tooltip on Enumeration 1 Keys End Point refers to enumeration 2. The fields behave as their level numbers say.
Outbound Job Fields Enabled (13)
Thirteen outbound job fields are exposed, covering the endpoint, method type, data sending methods, the outbound and return field lists and a raw JSON template that overrides the generated body.
Inbound Job Templates (1)
One inbound template ships, and it is a blank REST skeleton rather than a Cohesity job.
Job Template Configuration
Settings
NOTE: The template ships disabled. Nothing is retrieved until you configure an endpoint and enable a job.
NOTE: The authentication endpoint default shows the v1 public API prefix, /irisservices/api/v1/public/. Job endpoints on the same API follow that prefix, which is a useful starting point when you build the first job.
Outbound Job Templates (1)
One outbound template ships as a generic shell.
Job Template Configuration
Settings
Job Parameters and Enumeration
Rest POST API
Outbound fields list:
Return data fields: