Users

Object Overview

Users define individual or services that have access to View and the data stored therein.

Endpoint, URL, and Supported Methods

Objects are managed via the configuration server API at [http|https]://[hostname]:[port]/v1.0/tenants/[tenant-guid]/users

By default, the configuration server is accessible on port 8601.

Supported methods include: GET HEAD PUT DELETE

Structure

Objects have the following structure:

{
    "GUID": "default",
    "TenantGUID": "default",
    "FirstName": "Default",
    "LastName": "User",
    "FullName": "Default User",
    "Notes": "Default password is password",
    "Email": "[email protected]",
    "PasswordSha256": "************************************************************42d8",
    "Active": true,
    "CreatedUtc": "2024-07-10T05:09:31.000000Z"
}

Properties:

• GUID string globally unique identifier for the object
• TenantGUID string globally unique identifier for the tenant
• FirstName string user first name
• LastName string user last name
• FullName string derived string comprised of: first + ' ' + last
• Notes string administrator-supplied notes
• Email string email address for the user
• PasswordSha256 string the SHA-256 hash of the user's password
• Active bool indicates whether or not the user is considered active and able to be used
• CreatedUtc datetime timestamp from creation, in UTC time

Important: the user's password is never stored by View, but rather the SHA-256 hash within the PasswordSha256 property. As such this property is redacted when retrieving, enumerating, or updating the user object.

Create

To create, call PUT /v1.0/tenants/[tenant-guid]/users with the following properties using the configuration server: FirstName LastName Email PasswordSha256

curl -X PUT http://localhost:8601/v1.0/tenants/[tenant-guid]/users \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer [accesskey]" \
     -d '
{
  "FirstName": "Test",
  "LastName": "User",
  "Email": "[email protected]",
  "PasswordSha256": "5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8"
}'

Enumerate

Refer to the Enumeration page in REST API for details about the use of enumeration APIs.

Enumerate objects by using GET /v2.0/tenants/[tenant-guid]/users. The resultant object will appear as:

{
    "Success": true,
    "Timestamp": {
        "Start": "2024-10-21T02:36:37.677751Z",
        "TotalMs": 23.58,
        "Messages": {}
    },
    "MaxResults": 10,
    "IterationsRequired": 1,
    "EndOfResults": true,
    "RecordsRemaining": 16,
    "Objects": [
        {
            "GUID": "example-user",
            ... user details ...
        },
        { ... }
    ],
    "ContinuationToken": "[continuation-token]"
}

Read

To read an object by GUID, call GET /v1.0/tenants/[tenant-guid]/users/[user-guid]. If the object exists, it will be returned as a JSON object in the response body. If it does not exist, a 404 will be returned with a NotFound error response.

{
    "GUID": "default",
    "TenantGUID": "default",
    "FirstName": "Default",
    "LastName": "User",
    "FullName": "Default User",
    "Notes": "Default password is password",
    "Email": "[email protected]",
    "PasswordSha256": "************************************************************42d8",
    "Active": true,
    "CreatedUtc": "2024-07-10T05:09:31.000000Z"
}

Note: the HEAD method can be used as an alternative to get to simply check the existence of the object. HEAD requests return either a 200/OK in the event the object exists, or a 404/Not Found if not. No response body is returned with a HEAD request.

Update

To update an object by GUID, call PUT /v1.0/tenants/[tenant-guid]/users/[user-guid] with a fully populated object in the request body. The updated object will be returned to you.

Note: certain fields cannot be modified and will be preserved across updates.

Request body:

{
    "FirstName": "Updated",
    "LastName": "User",
    "Notes": "Default password is password",
    "Email": "[email protected]",
    "PasswordSha256": "5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8"
}

Response body:

{
    "GUID": "b9a4e282-7add-4951-8654-d61ad49f6130",
    "TenantGUID": "default",
    "FirstName": "Updated",
    "LastName": "User",
    "FullName": "New User",
    "Notes": "Default password is password",
    "Email": "[email protected]",
    "PasswordSha256": "5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8",
    "Active": true,
    "CreatedUtc": "2024-10-21T14:08:41.281865Z"
}

Delete

To delete an object by GUID, call DELETE /v1.0/tenants/[tenant-guid]/users/[user-guid]. Deletion of a user triggers deletion of associated credential objects.