Cloud Connectivity

Note

The RADKit Cloud endpoints are subject to change. Always refer to the latest documentation or contact support for the most up-to-date information.

RADKit Cloud Endpoints

RADKit Client and RADKit Service can communicate with one another through RADKit Cloud. Specifically, RADKit Client and Service will connect to RADKit Cloud for the following purposes:

  • RADKit Service to enroll and acquire a Service ID

  • RADKit Service to authenticate to RADKit Cloud

  • RADKit Service to accept remote users

  • RADKit Client to authenticate to RADKit Cloud

  • RADKit Client to connect to RADKit Service

RADKit Cloud Endpoint

Endpoint

TLS Policy

Description

https://prod.radkit-cloud.cisco.com

TLS1.3 / TLS_AES_128_GCM_SHA256

Necessary for RADKit Client-Service remote connectivity

SR Attachment Endpoints

By request from a RADKit Client, RADKit Service can attach data directly to a Service Request (SR). RADKit Client can also autonomously attach data to an SR. This is done through a mechanism called CX Drive (CXD).

For this capability, RADKit Client needs a CXD token which can be user-provided or generated by RADKit Client if necessary.

CXD Endpoints

Endpoint

TLS Policy

Description

https://cxd.cisco.com

TLS1.2 / ECDHE-RSA-AES128-GCM-SHA256

RADKit Client or Service to attach data to a Service Request

https://cxd-token.cxapps.cisco.com

TLS1.2 / ECDHE-RSA-AES128-GCM-SHA256

RADKit client to generate upload CXD tokens

Note

On the Cisco IQ domains, CX Drive is reached through endpoints proxied by the cloud instance itself (https://<region>.iq.cisco.com/radkit/cxd for uploads and https://<region>.iq.cisco.com/radkit/cxd-token for upload tokens, with the same TLS policy as the RADKit Cloud endpoint above) rather than through the two hosts listed here, and the proxy forwards the requests to cxd.cisco.com and cxd-token.cxapps.cisco.com respectively. Both RADKit Client and RADKit Service need egress to it: the Service uploads using the URL that the Client hands it. SCP, SFTP and FTP uploads always go to cxd.cisco.com directly. Deployments that narrowed cloud_client.upload_allowed_hosts have to allow the IQ endpoint as well.

Endpoints API

The information above is available without authentication, in JSON format at the following endpoint: