2 Prerequisites
The MyID Application server must have access to the Microsoft Azure SQL Database service. You must ensure that the Azure firewall settings allow access.
Note: For SQL Server, MyID requires that you install the Full Text Search option for the SQL Server Engine. This feature is built in to Microsoft Azure SQL database, so you do not need to configure it separately.
Before you begin the MyID installation, you must have:
-
Already-created databases to be populated during the installation.
You must create a database for the main MyID installation, and an additional database for the MyID authentication database. If you are using a separate archive database, you must also create a database for that purpose.
Note: You are recommended to create the databases manually using Azure portal, PowerShell, or SQL Management Studio for the correct size of database to be configured. A minimum database size of S2 is recommended.
-
You must create two logins that can create schema objects:
-
The MyID user – used to control the main MyID database. Also requires permissions to the authentication database.
-
MyID authentication user – used to control the authentication database. Also requires read-only permissions to the main MyID database.
These logins must have the following permissions on each database:
-
MyID user on the MyID database:
-
db_datareader – required for reading data.
-
db_datawriter – required for writing data.
-
db_owner – required for creating schema objects; for example, temporary tables created by stored procedures.
-
-
MyID user on the authentication database:
-
db_datareader – required for reading data.
-
db_datawriter – required for writing data.
-
db_owner – required for creating schema objects; for example, temporary tables created by stored procedures.
-
-
MyID Authentication user on the MyID database:
-
db_datareader – required for reading data.
-
-
MyID Authentication user on the authentication database:
-
db_datareader – required for reading data.
-
db_datawriter – required for writing data.
-
db_owner – required for creating schema objects; for example, temporary tables created by stored procedures.
-
-