Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve users associated with a specific asset. It is useful in scenarios where you need to query and manage user information linked to assets within an enterprise or organizational context. For example, it can be used to fetch all users who have access to a particular digital asset or resource, filter them based on certain conditions, paginate through large user lists, or order the results by specific fields.

Properties

Name Meaning
X USER ID The User ID header value required for authentication or identification in the request.
Condition A query string to filter the users retrieved based on specified criteria.
Skip Number of records to skip, useful for pagination.
Limit Maximum number of user records to return.
Order By Field(s) by which to order the returned user list.

Output

The node outputs JSON data containing the list of users associated with the specified asset. Each item in the output corresponds to a user record matching the query parameters. The structure typically includes user details as provided by the Connect Secure API response. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • The node uses the OpenAPI specification bundled internally to define its operations and properties.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication errors. Ensure the correct user ID is supplied.
  • Invalid query condition syntax: If the Condition parameter is malformed, the API may reject the request or return no results. Verify the query syntax matches the API's expected format.
  • Pagination issues: Incorrect use of Skip and Limit could result in unexpected subsets of data or empty responses. Adjust these values carefully when paginating.
  • Ordering errors: Providing invalid field names in Order By might cause the API to ignore the parameter or return errors. Use valid sortable fields as per API documentation.
  • API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval. Check network access and credential validity.

Links and References

Discussion