Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Application Baseline" resource to retrieve application baseline rules. It is designed to query and fetch rules that define baseline configurations or policies for applications, which can be useful in scenarios such as compliance monitoring, security auditing, or configuration management.

Typical use cases include:

  • Fetching a filtered list of baseline rules based on specific conditions.
  • Paginating through large sets of baseline rules using skip and limit parameters.
  • Sorting the retrieved rules by specified fields.

For example, a user might want to retrieve all baseline rules related to a particular application version or environment, limiting results to 50 entries, skipping the first 100, and ordering them by creation date.

Properties

Name Meaning
X USER ID User Id required for authentication or identification in the API request header.
Condition Query condition to filter the baseline rules (e.g., filtering by attributes or criteria).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By Field(s) by which to order the returned baseline rules.

Output

The node outputs JSON data representing the retrieved application baseline rules. The structure typically includes an array of rule objects matching the query parameters. Each object contains details about a baseline rule according to the API's schema.

If binary data were involved (not indicated here), it would represent files or attachments related to the baseline rules, but this node focuses on JSON data output.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • Depends on the external Connect Secure API service endpoint.
  • The node uses the OpenAPI specification bundled internally to build its properties and handle routing.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID in the header; ensure this is provided and correct.
  • Invalid query parameters: Conditions, skip, limit, and order_by must conform to the API's expected formats; incorrect values may cause errors or empty responses.
  • API connectivity issues: Network problems or incorrect credentials will prevent successful data retrieval.
  • Empty results: If no baseline rules match the condition, the output will be empty; verify the query condition correctness.

Links and References

Discussion