Skip to content

cc_profile

Configuration for Cloud Profile resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
client_secret<String>Read-writeSecret.
Minimum length = 1
Maximum length = 128
client_id<String>Read-writeID.
Minimum length = 1
Maximum length = 128
tenant_id<String>Read-writeTenant Id of cloud profile.
Minimum length = 1
Maximum length = 128
id<String>Read-writeId is system generated key for all the cloud profiles.
name<String>Read-onlyProfile Name.
state<String>Read-onlyProfile state.
email<String>Read-onlyEmail address of cloud profile holder.
customer_id<String>Read-onlyCustomer ID of the cloud profile holder.
is_set<Boolean>Read-onlyTrue, if this profile is updated by user.
end_point<String>Read-onlyEnd point of the service.

Operations

(click to see Properties)

GET (ALL)| GET| UPDATE

Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

Note:

Mandatory parameters are marked in red and placeholder content is marked in <green>.

get (all)

URL: https://<MGMT-IP>/nitro/v1/config/cc_profile

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "cc_profile":[{
"name":<String_value>,
"client_secret":<String_value>,
"client_id":<String_value>,
"state":<String_value>,
"email":<String_value>,
"tenant_id":<String_value>,
"customer_id":<String_value>,
"is_set":<Boolean_value>,
"id":<String_value>,
"end_point":<String_value>}]}

get

URL: https://<MGMT-IP>/nitro/v1/config/cc_profile/id_value<String>

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "cc_profile":[{
"name":<String_value>,
"client_secret":<String_value>,
"client_id":<String_value>,
"state":<String_value>,
"email":<String_value>,
"tenant_id":<String_value>,
"customer_id":<String_value>,
"is_set":<Boolean_value>,
"id":<String_value>,
"end_point":<String_value>}]}

update

URL: https://<MGMT-IP>/nitro/v1/config/cc_profile/id_value<String>

HTTP Method: null

Request Payload:

{cc_profile:{
<b>"id":<String_value></b>,
"client_id":<String_value>,
"client_secret":<String_value>,
"tenant_id":<String_value>}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "cc_profile":[{
"name":<String_value>,
"client_secret":<String_value>,
"client_id":<String_value>,
"state":<String_value>,
"email":<String_value>,
"tenant_id":<String_value>,
"customer_id":<String_value>,
"is_set":<Boolean_value>,
"id":<String_value>,
"end_point":<String_value>}]}