Help Center> ROMA Connect> API Reference> Service Integration APIs> Client Configuration> Configuring Access Control for an App
Updated on 2023-06-29 GMT+08:00
View PDF

Configuring Access Control for an App

Function

This API is used to configure access control for a client configuration.

URI

PUT /v2/{project_id}/apic/instances/{instance_id}/apps/{app_id}/app-acl

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID. For details about how to obtain the project ID, see Appendix > Obtaining a Project ID in the ROMA Connect API Reference.

instance_id

Yes

String

Instance ID.

app_id

Yes

String

Application ID

Request Parameters

Table 2 Request header parameters

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

User token, which can be obtained by calling the IAM API (value of X-Subject-Token in the response header).
Table 3 Request body parameters

Parameter

Mandatory

Type

Description

app_acl_type

Yes

String

Access control type.

  • PERMIT (whitelist)

  • DENY (blacklist)

app_acl_values

Yes

Array of strings

ACL policy value. The value can be an IP address, IP address segment, or CIDR block. Use hyphens (-) to separate IP address segments.

Response Parameters

Status code: 201

Table 4 Response body parameters

Parameter

Type

Description

app_id

String

App ID.

app_acl_type

String

Access control type.

  • PERMIT (whitelist)

  • DENY (blacklist)

app_acl_values

Array of strings

ACL policy value. The value can be an IP address, IP address segment, or CIDR block. Use hyphens (-) to separate IP address segments.

Status code: 400

Table 5 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 401

Table 6 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 403

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 404

Table 8 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Status code: 500

Table 9 Response body parameters

Parameter

Type

Description

error_code

String

Error code.

error_msg

String

Error description.

Example Requests

{
  "app_acl_type" : "PERMIT",
  "app_acl_values" : [ "192.168.0.1", "192.168.0.5-192.168.0.10", "192.168.0.100/28" ]
}

Example Responses

Status code: 201

Ok

{
  "app_id" : "9ed8b7fe84224de681e7d7a5587e76dc",
  "app_acl_type" : "PERMIT",
  "app_acl_values" : [ "192.168.0.1", "192.168.0.5-192.168.0.10", "192.168.0.100/28" ]
}

Status code: 400

Bad Request

{
  "error_code" : "APIG.2012",
  "error_msg" : "Invalid parameter value,parameterName:app_id. Please refer to the support documentation"
}

Status code: 401

Unauthorized

{
  "error_code" : "APIG.1002",
  "error_msg" : "Incorrect token or token resolution failed"
}

Status code: 403

Forbidden

{
  "error_code" : "APIG.1005",
  "error_msg" : "No permissions to request this method"
}

Status code: 404

Not Found

{
  "error_code" : "APIG.3004",
  "error_msg" : "App 9ed8b7fe84224de681e7d7a5587e76dc does not exist"
}

Status code: 500

Internal Server Error

{
  "error_code" : "APIG.9999",
  "error_msg" : "System error"
}

Status Codes

Status Code

Description

201

Ok

400

Bad Request

401

Unauthorized

403

Forbidden

404

Not Found

500

Internal Server Error

Error Codes

See Error Codes.

Parent topic: Client Configuration