AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, "Authentication Create" under the "Authentication" resource, is designed to create or manage authentication sessions or tokens by interacting with an external API. It allows users to specify additional query parameters that control how organizations related to the user are handled during authentication creation. This can be useful in scenarios where you want to authenticate a user and simultaneously filter or limit the scope of organizations returned or checked as part of the authentication process.

Practical examples include:

  • Creating an authentication token while only returning the default organization the user belongs to.
  • Limiting the number of organizations returned for performance or data minimization reasons.
  • Skipping checks for pre-existing users to speed up the authentication process when such validation is unnecessary.

Properties

Name Meaning
Additional Query Parameters Optional query parameters to customize the authentication request:
- Default Only Return only the default organization the user is member of (true/false). Defaults to true.
- Direct Only Return only direct organizations the user is member of (true/false). Defaults to true.
- Limit Organizations Maximum number of organizations to be returned. Defaults to 0 (no limit).
- Skip User Checks If false, will skip checking for pre-existing users. Defaults to true (meaning it does not skip checks).

Output

The node outputs JSON data representing the result of the authentication creation request. This typically includes details about the created authentication session or token, and possibly information about organizations filtered according to the query parameters provided.

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

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The base URL for API requests is https://api.dnsfilter.com.
  • The node uses standard HTTP headers including Accept: application/json and Content-Type: application/json.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid values for query parameters (e.g., non-boolean for boolean fields) may result in API errors.
    • Network connectivity issues can prevent successful API calls.
  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; ensure the correct API key is configured.
    • Validation errors from the API may occur if query parameters are malformed; verify parameter types and values.
    • Timeout or connection errors suggest network problems; check internet connectivity and API endpoint availability.

Links and References

Discussion