Actions2
Overview
This node performs OTP verification for the OKMAN login system, which is part of the MISA Act API integration. It is used to verify a one-time password (OTP) sent to a user during the login process, enabling secure authentication. This node is beneficial in workflows where multi-factor authentication is required, such as logging into financial or enterprise applications that use MISA's services. For example, after a user initiates a login, this node can be used to verify the OTP they received, ensuring the login is authorized before proceeding.
Use Case Examples
- Verifying OTP during a secure login process to MISA's AMIS app.
- Automating multi-factor authentication workflows in enterprise applications using MISA's API.
Properties
| Name | Meaning |
|---|---|
| User Agent | The user agent string to be used in HTTP headers for requests, simulating the client browser or device. |
| Culture | The culture or language code (e.g., 'vi' for Vietnamese) used in requests to localize responses. |
| Tenant ID | Optional tenant identifier for multi-tenant environments. |
| Device ID (UUID) | Unique device identifier used to track the device in the authentication process. |
| Proxy | Optional proxy server address to route HTTP requests through. |
| Raw Cookies (k=v; k2=v2) | Optional raw cookie string copied from a browser session to maintain session state. |
| Token | The authentication token received from the initial login step, required for OTP verification. |
| OTP | The one-time password code to verify the user's identity. |
| Use App Authenticator | Boolean flag indicating whether to use an app-based authenticator for OTP. |
| Remember | Boolean flag indicating whether to remember the device for future logins. |
| Cookies Seed (JSON or k=v; k2=v2) | Optional JSON or raw cookie string used to seed the cookie jar for session continuity. |
Output
JSON
success- Boolean indicating if OTP verification was successful.credentialId- ID of the saved credential created after successful OTP verification.deviceId- The device ID used during the OTP verification process.culture- The culture code used in the request.tenantId- The tenant ID used in the request.error- Error message in case OTP verification fails or an error occurs.
Dependencies
- Requires an API key credential for the n8n API to save credentials after successful OTP verification.
Troubleshooting
- Ensure the Device ID is provided from the login step; missing Device ID will cause errors.
- Verify that the Token and OTP values are correct and not expired.
- If OTP verification fails with status 401, 400, or 404, the node attempts an alternative verification method; if both fail, check the OTP and token validity.
- Check that cookies are correctly seeded if using Cookies Seed input; malformed cookies may cause session issues.
- Network or proxy issues may cause request failures; verify proxy settings if used.