Mira Verify Token icon

Mira Verify Token

Verify access token with Mira App Server

Mira Verify Token

AI-generated

Overview

The "Mira Verify Token" node is designed to verify an access token against the Mira App Server. It sends a verification request to the server to confirm whether the provided token is valid. This node is useful in workflows where you need to authenticate or validate user sessions, API tokens, or other access credentials before proceeding with further actions.

Practical examples:

  • Validating a user's access token before fetching sensitive data.
  • Checking token validity as part of an authentication flow.
  • Ensuring that an API token has not expired or been revoked before making API calls.

Properties

Name Meaning
Token Source Choose where to get the access token from: "From Credentials" (use token from stored credentials) or "From Input Data" (use token from input or enter directly).
Server URL The URL of the Mira App Server to which the verification request will be sent. Required if "Token Source" is set to "From Input Data". Default is http://localhost:8081.
Access Token The access token to verify. Can be provided directly or via expressions referencing input data. Required if "Token Source" is set to "From Input Data".

Output

The node outputs JSON data representing the response from the Mira App Server's token verification endpoint (/api/auth/verify). This typically includes information about the token's validity and possibly associated user or session details.

If the token is valid, the output JSON will confirm successful verification; if invalid, it will indicate failure or error details.

The node does not output binary data.

Dependencies

  • Requires access to a Mira App Server instance reachable at the specified Server URL.
  • If using "From Credentials" for the token source, the node depends on having a configured API key credential containing the access token.
  • Network connectivity to the Mira App Server is necessary.
  • No additional external libraries beyond those bundled with the node are required.

Troubleshooting

  • Common issues:

    • Incorrect or expired access token leading to failed verification.
    • Misconfigured Server URL causing connection errors.
    • Missing or improperly set access token when using "From Input Data".

  • Error messages:

    • Authentication failures usually return HTTP 401 or similar status codes indicating invalid token.
    • Connection errors may occur if the Server URL is unreachable or incorrect.

  • Resolutions:

    • Ensure the access token is current and correctly provided.
    • Verify the Server URL is correct and the Mira App Server is running.
    • When using input data for the token, confirm the token field exists and is properly referenced.

Links and References

  • Mira App Server API documentation (for /api/auth/verify endpoint) — consult your Mira App Server docs for detailed response formats and usage.
  • n8n documentation on handling credentials and expressions for dynamic token input.

Discussion