Authentication Table

Overview

• Purpose: To store authentication details such as email, password, token signature, and reset key.

• Recommendation: It's recommended to use a users table for this purpose.

Use Data → Authentication to search the table's customers, suspend or resume access and manage independent sessions. See Customer authentication tools for the commands, login compatibility and session limits. These controls use this same table.

Requirements for Authentication Table

1. Mandatory for Endpoints: An authentication table is necessary for generating authentication endpoints.

2. Unique to Workspace: You can assign only one authentication table per workspace.

How to Assign an Authentication Table

Creating a New Table

When creating a new table, you have an option to designate it as the authentication table:

1. Enable Authentication: Select "Enable" in the Authentication Table dropdown during table creation.

Updating an Existing Table

You can also update an existing table to become an authentication table by adjusting its settings in the table configuration.

Fields Generated by Authentication Table

When you generate authentication endpoints, the following fields are automatically created in the authentication table:

• email: Stores user email addresses.

• password: Stores user passwords in a hashed format for security.

• token_signature: Stores token signatures as hashed values for added security.

• reset_key: Stores reset keys in a hashed format for password reset operations.

  

Security Identifiers

In the database view:

• The authentication table can be easily identified by a security icon on its table details.

Summary

To summarize, the authentication table in Twidget:

• Stores critical authentication data.

• Is a prerequisite for generating authentication endpoints.

• Introduces security features by hashing sensitive information.

• Can be easily identified and configured within the workspace.