Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve SELinux settings related to assets. It is designed to query and fetch SELinux configuration data, which can be useful for security auditing, compliance checks, or system configuration management within an organization's infrastructure.

Typical use cases include:

  • Fetching SELinux status or policies applied on various assets.
  • Filtering SELinux settings based on specific conditions or criteria.
  • Paginating through large sets of SELinux records.
  • Ordering the results by specified fields for easier analysis.

For example, a user might want to retrieve all SELinux settings where a particular policy is enforced, skip the first 10 records, limit the output to 50 entries, and order them by creation date.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter the SELinux settings returned by the API.
Skip Number of records to skip in the result set (used for pagination).
Limit Maximum number of records to return (used for pagination).
Order By Field name(s) to order the results by (e.g., "created_at", "name").

Output

The node outputs JSON data representing the retrieved SELinux settings from the Connect Secure API. Each item in the output corresponds to a SELinux setting record matching the query parameters.

The structure typically includes fields describing SELinux configurations, such as policy names, enforcement modes, associated asset identifiers, timestamps, and other relevant metadata.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API key or token credential configured in n8n for authentication.
  • The node depends on the @devlikeapro/n8n-openapi-node package for OpenAPI integration.
  • The bundled OpenAPI specification (openapi.json) defines the API endpoints and operations.

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 or authorization errors. Ensure this property is correctly set.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may lead to empty results or API errors. Validate the syntax according to the API's query language.
  • Pagination issues: Setting Skip or Limit to inappropriate values (e.g., negative numbers) could cause unexpected behavior or errors.
  • Ordering errors: Using invalid field names in Order By may result in API errors or default ordering.
  • API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval.

Links and References

Discussion