Associate User Group with Resources

This API is used to associate one or more resources to a user group.

Before you begin

  • Session ID is obtained from the login API.
  • Ensure that the session ID is valid and has not expired.

Request Structure

Endpoint: /usergroup-updateResource
Type: POST
Sample URL: https://<IP/HostName/TenantName>:<GWPORT>/avxapi/usergroup-updateResource?gwsource=web

To understand the elements of the sample URL, click here.

Headers:
Content-Type: application/json
Table 1. Input Parameters
Name Description
sessionId (or) Token

Header

(Mandatory) Use either Session Id or Token received after login.

Type: String

Example: "sessionId": "ce7f1a14-2bf9-4e4a-89a8-bc780a255813"

gwsource

Query

(Mandatory) Source from which the request is triggered. The values can be:
  • web
  • external

Type: String

Payload

String

(Mandatory) Input data for request body in application/json format. For payload details, see Payload section.

Payload

Name Description
name

String

(Mandatory) Name of the user group.

Example: "internal90"

assignList

Array

(Optional) List of resources to be assigned to the user group.

Example: "resource_2"

unassignList

Array

(Optional) List of resources to be unassigned from the user group. .

Example: "resource_1"

Response Structure

  • Status Code: 200 OK
  • Message: Successfully associated user group - resource
  • Headers:
    • Content-Type: application/json
Table 2. Response Parameters
Name Description
response Contains the response attributes for getting details about a user group.
message Success message or failure description in case of error.
appStatusCode Application specific status code for the response. Will be non-null for failure response.
tags More info in case of failure response.

Status Codes

HTTP Code appStatusCode Response Message
200 OK null Successfully associated user group - resource
400 Bad Request ACCT_USERGROUP_001 Mandatory field 'userGroupName' is missing or empty
404 Not Found ACCT_USERGROUP_027 UserGroup not found.

Sample Request/Response

Use Case

Get the details about a user group with the name usergroup_1.

Sample Request
https://<IP/HostName/TenantName>:<GWPORT>/avxapi/usergroup-updateResource?gwsource=external
Request Payload
{
 "payload": {
   "name": "testgroup",
   "assignList" : [
     "resource_2"
    ],
   "unassignList": [
     "resource_1"
   ]
 }
}
Sample Response
{
 "response": "Updating usergroup with resource(s) successful",
 "message": "Updating usergroup with resource(s) successful",
 "appStatusCode": null,
 "tags": null,
 "headers": null
 }

Reference

Understanding the sample URL:
  • IP/HostName/TenantName: Replace with the actual IP address, hostname, or tenant name based on the specific configuration in AppViewX.
    • IP: A unique identifier assigned to each device connected to a computer network that uses the Internet Protocol for communication

      The IP address will be included in the endpoint URL for an on-prem deployment.

    • HostName: A human-readable label assigned to a device (host) on a network

      The hostname will be included in the endpoint URL for an on-prem deployment.

    • TenantName: An identifier label for a tenant given to indicate which tenant's data the API request will access/modify

      The tenant name will be included in the endpoint URL for a SaaS deployment.

  • GWPORT: AppViewX gateway port

    A gateway port refers to a network port through which data is sent and received to communicate with a gateway in an on-prem deployment.

    Example: 31443

  • avxapi: Path parameter value (static) that is part of the endpoint's URL
  • Endpoint: Endpoint of the API, for example: execute-hook
  • gwsource: Source or origin of a gateway, for example: external.