Audit Logging¶

Introduction¶

The Audit Logging page of the Management Console allows an administrator of a Harmony organization to retrieve logs of activity taking place in Management Console and Cloud Studio. To access the Audit Logging page, log in to the Jitterbit Harmony Portal, then use the Harmony Portal menu in the top left and navigate to Management Console > Audit Logging:

As an alternative to viewing audit logs on the Management Console Audit Logging page, you can retrieve audit logs using a REST API. The Audit Log Service API is described later on this page.

Prerequisites¶

To enable and view audit logs, you must be a member of a role with Admin permission in the organization. For information on roles and permissions, see Managing Permissions, Roles, and Members.

Enabling Audit Logging¶

To enable and disable audit logging for a specific organization:

1. Log in to the Jitterbit Harmony Portal and go to Management Console > Organizations.
2. Select the appropriate organization from the menu in the top navigation bar.
3. Use the Action menu for that organization to select Edit Organization Policies.
4. Select Enable Audit Logging and click Save to save the organization polices and to turn on audit logging for the organization.

Audit Logging Page Header¶

The header along the top of the Audit Logging page includes date and time filters, a search bar, and additional options:

Date and Time Filters¶

By default, audit log data from the past two days are displayed in the audit logging table.

Use the From and To calendar fields to filter the audit logging data by date and time:

• From: Click the calendar icon to adjust the starting date for the audit logs. Click the clock icon to adjust the starting time for the audit logs.

• To: Click the calendar icon to adjust the ending date for the audit logs. Click the clock icon to adjust the ending time for the audit logs.

Once the desired date and times have been selected, click the search button in the search bar to populate the audit log table with the desired audit logs.

Searching¶

The search bar allows you to filter the logs by the search criteria provided below:

Search Criteria¶

These are examples of the search criteria that can be used:

Combining Searches¶

Searches can contain a combination of criteria. Combined search criteria must be separated by a semi-colon (;) between each criterion. These are examples of valid combined searches:

action=update;environment=production

environmentid=123456;action=create

Additional Options¶

Additional audit log options display on the right side of the page next to the search bar:

• Download: Click to download a ZIP file containing a CSV file with the current audit log data based on the applied filters and search criteria.

• Down Arrow: Click to filter the columns that are displayed in the audit log table. By default, all columns are selected to be displayed:

  

Viewing Audit Logs¶

Each row in the audit logs table displays audit logging data of activity taking place in Management Console and Cloud Studio:

• Username: The username of the user performing the activity.

• Operation Name: The name (path) of the operation (the API call to Jitterbit Harmony) that was logged.

• Action: The action performed by the user, one of Create, Delete, Update, or Query:

  • Create: Indicates the user created new data in the contents of a page in Management Console or a project in Cloud Studio. For example, creating a new agent in Management Console or deploying a project in Cloud Studio would be Create actions.
  • Delete: Indicates the user deleted data from the contents of a page in Management Console or a project in Cloud Studio. For example, deleting an agent in the Management Console or deleting a project from Cloud Studio would be Delete actions.
  • Update: Indicates the user updated the contents of a page in Management Console or a project in Cloud Studio. For example, changing the name of an agent in Agents > Agents would be an Update action.
  • Query: Indicates the user viewed the contents of a page in Management Console or a project in Cloud Studio. For example, viewing the list of projects in Cloud Studio would be a Query action.

• Time: The timestamp of the activity. Times are displayed in your browser's time zone.

• Environment ID: The environment ID where the activity takes place.

• Environment Name: The name of the environment where the activity takes place.

  Note

  Empty columns for Environment ID and Environment Name indicate that the activity is not related to a specific environment.

Audit Log Service API¶

As an alternative to viewing audit logs on the Management Console Audit Logging page, you can retrieve audit logs using a REST API. This requires the use of either command line utilities such as curl or applications such as Postman.

To use the Audit Log Service API, after enabling audit logging for the organization (described earlier on this page), follow these steps:

1. Retrieve an authentication token using the User Service Controller API. This token is required in order to use the Audit Log Service API.
2. Retrieve logs using the Audit Log Service API.

Retrieving an Authentication Token¶

Retrieving an authentication token requires the use of the User Service Controller API. An example request showing logging in to the NA region and retrieving the authorization token:

curl --location --request PUT 'https://na-east.jitterbit.com/jitterbit-cloud-restful-service/user/login' \
--header 'Content-Type: application/json' \
--data-raw '{
    "email": "alice@jbexample.com",
    "password": "Jitterbit4Ever!"
}'

Base URL¶

The base URL depends on the region that the organization is located in:

Headers¶

These headers are required:

Body Parameters¶

These required parameters are passed in the body of the request:

Response Body¶

The returned response body contains a list of the organizations that the user is associated with in addition to the authentication token ("authenticationToken"). This token is required for subsequent authorization with the Audit Logging API. In this example, the authentication token is "1_70dfe7f7-1d47-4ad5-be5d-bc4a222dd2g4". The organization ID is shown as "20980" for the first organization that this user belongs to. A pretty-printed example of the response:

{
  "status": true,
  "operation": "User login",
  "authenticationToken": "1_70dfe7f7-1d47-4ad5-be5d-bc4a222dd2g4",
  "serverUrl": "https://na-east.jitterbit.com",
  "cloudAppsUrl": "https://na-east.jitterbit.com",
  "orgAttrs": [
    {
      "orgId": "20980",
      "orgName": "JB Example Company",
      "orgZoneUrl": "https://na-east.jitterbit.com"
    },
    {
      "orgId": "20970",
      "orgName": "example@jbexample.com",
      "orgZoneUrl": "https://na-east.jitterbit.com"
    }
  ],
  "defaultOrgId": "20980",
  "sessionTimeoutInSeconds": 14400
}

Retrieving Audit Logs¶

Once you have the authentication token, the organization ID, and a time period you are interested in, you can retrieve audit logs. An example showing retrieving all records beginning on January 1, 2021 and including the detailed version of the records:

curl --request POST 'https://api.na.jitterbit.com/v1/auditlog?detail=true' \
--header 'accept: application/json' \
--header 'authToken: 1_70dfe7f7-1d47-4ad5-be5d-bc4a222dd2g4' \
--header 'Content-Type: application/json' \
--data-raw '{
    "queryParams": {
        "organization_id": "20980"
    },
    "range": {
        "fromTimestamp": "2021-01-01T00:00:00.000Z",
        "toTimeStamp": "9999-01-01T00:00:00.000Z"
    }
}'

Base URL¶

The base URL depends on the region that the organization is located in:

Endpoints¶

The Audit Log Service has these endpoints (APIs) available:

URL Parameters¶

These parameters can be passed in the URL:

Headers¶

These headers can be used in the request:

Body Parameters¶

These parameters can be passed in the body of the request:

Example¶

This example uses the auditlog/download endpoint to retrieve all records for organization 20980, with an action of QUERY, beginning as of January 1, 2021, including the detailed version of the records, and downloaded as CSV in a compressed (ZIP) file format to an output file:

curl --request POST 'https://api.na.jitterbit.com/v1/auditlog/download?detail=true' \
--output 'download.zip' \
--header 'accept: application/zip' \
--header 'authToken: 1_70dfe7f7-1d47-4ad5-be5d-bc4a222dd2g4' \
--header 'Content-Type: application/json' \
--data-raw '{
    "queryParams": {
        "organization_id": "20980",
        "action": "QUERY"
    },
    "range": {
        "fromTimestamp": "2021-01-01T00:00:00.000Z",
        "toTimeStamp": "9999-01-01T00:00:00.000Z"
    }
}'

Example Log Output¶

This is a fragment of the output returned when using the auditlog endpoint to receive records in a JSON format:

. . .
  {
    "username": "alice@jbexample.com",
    "organization_id": "20980",
    "organization_name": "JB Example Company",
    "operation_name": "/jitterbit-cloud-restful-service/dashboard/statistics/todayssourcefilestats/20980/08-27-2021%252012:00:00%2520-0600",
    "action": "QUERY",
    "action_timestamp": "2021-08-27T14:23:36.212Z",
    "environment_ids": null,
    "environment_names": null,
    "user_id": "1039951"
  },
  {
    "username": "alice@jbexample.com",
    "organization_id": "20980",
    "organization_name": "JB Example Company",
    "operation_name": "/jitterbit-cloud-restful-service/project/env/list/showallparams/20980",
    "action": "QUERY",
    "action_timestamp": "2021-08-27T14:23:36.520Z",
    "environment_ids": [
      "132520",
      "132530"
    ],
    "environment_names": [
      "Development",
      "Default Environment"
    ],
    "user_id": "1039951"
  },
  {
    "username": "alice@jbexample.com",
    "organization_id": "20980",
    "organization_name": "JB Example Company",
    "operation_name": "/jitterbit-cloud-restful-service/dashboard/statistics/entitlements/20980",
    "action": "QUERY",
    "action_timestamp": "2021-08-27T14:23:37.417Z",
    "environment_ids": null,
    "environment_names": null,
    "user_id": "1039951"
  },
. . .