Authenticate User Node
| Description | The Authenticate User node authenticates a user by performing a bind operation on IO with the supplied username and password. A successful bind confirms the validity of the credentials and allows the flow to continue. |
| Available in | Authentication, Admin, Self Service, API, Consent, Library, Custom, User Defined |
| Node Name | Authenticate User |
The set of available options may depend on the flow category or type in which the node is used.
User Binding Configurations
User Binding Configurations
This section allows you to configure **how the user is bound to the session**. ### Username You can bind the user either by **username** or by a specific **attribute**. In both cases, the corresponding value must be specified (can use a variable from the form node, e.g. `{{form.username}}` and `{{form.password}}`). An additional **Ignore case** option is available to perform the binding without considering letter case differences. ### Password Configure the **password**, including an optional flag to **verify password expiration**. When this option is enabled, you can specify a **TTL (in seconds)** to define the validity period. ### Attributes to retrieve from the user store Select which **user attributes** should be retrieved from the user after the binding process.User Identify Rule
Condition to map the user retrieved from the node to the user in the session
The **User Identity Rule** is the condition used to **match** the user retrieved by the node with the user stored in the **current user session**. See [Common Configurations — User Identify Rule]({filename}/pages/io/io-nodes/io-node-types/common-configurations.md#user-identify-rule) for full details and attribute manipulation functions.Save in Session
Session attribute mapping
The **Save in Session** option is used to persist data within the IO user session. The **Session Attribute Mapping** section allows mapping IO attributes to specific values. Multiple mappings can be defined; they are stored in the **IO user session** at the end of the flow. Rules are defined as: `IO attribute : value retrieved from the node` Example: `username: uid` See [Common Configurations — Save in Session]({filename}/pages/io/io-nodes/io-node-types/common-configurations.md#save-in-session) for details.Save in the Flow Store
Save in the Flow store
Attributes generated or retrieved from the node can be saved **into a variable** and reused by other nodes in the flow by referencing them as `{{variable.attribute}}`. See [Common Configurations — Save in the Flow Store]({filename}/pages/io/io-nodes/io-node-types/common-configurations.md#save-in-the-flow-store) for details.Default Output Node
- Success
- Wrong Credentials
- User Pending
- User Locked
- User not found
- Password expired
- Failure
