Database requirements
The ESET Secure Authentication On-Prem SDK stores a user's 2FA data in your existing database as a string. You will therefore need to add a column capable of storing unicode strings of varying length.
MySQL users |
We recommend that you use the TEXT datatype |
Postgres users |
We recommend that you use the character_data datatype |
Oracle users |
We recommend that you use the NCLOB datatype |
Microsoft SQL Server users |
We recommend that you use the nvarchar(max) datatype |
If you do not have a mobile telephone number field for each user, it is highly recommended that you create a field capable of storing mobile numbers (numeric strings of varying length). This will help to ensure compatibility with future releases.