The default level of security for your InterAction system is SQL Server Authentication. SQL Server requires a user to enter a valid account name and password to access the database. Therefore, the InterAction software must also provide the database with a valid account name and password when connecting, just like any other “user.”
By default, InterAction products connect to the InterAction database using SQL Server authentication. In some instances, your organization may prefer using Windows Authentication when making these connections. For details, see the “Using SQL Server Windows Authentication in an InterAction Environment” on the InterAction Support site.
When connecting to the database server, InterAction logs in to the server using a database “user” account. InterAction uses two different database accounts - a low security account (IDCDFLT) and a high-security account (IDCAPP). Both of these accounts are automatically created when you initialize an InterAction database. Note that each InterAction user does not require a separate database account.
When a user starts InterAction, the software connects to the InterAction database using the low security account (IDCDFLT). The software obtains information from within tables in the database to make the high security connection, then ends the low-security connection and re-connects using the high-security (IDCAPP) account. InterAction connects to the database as IDCAPP regardless of which InterAction user is logging in to the system. Separate database accounts are not needed for each user in your organization.
The IDCAPP account is created with a default password that you should change for security reasons. Always change this password using InterAction Administrator. If you change to Windows Authentication later, the IDCAPP login will be replaced by the appropriate Windows login.
Never change the IDCAPP password directly on the database server using the database tools. If you do, the password stored by InterAction (in encrypted format) no longer matches the password on the database server and InterAction cannot connect to the server.
The IDCDFLT account is also created with a password, but do not change this password. If you do change this password, InterAction is not able to connect to the database.
Do not, under ANY circumstances, change the password for the IDCDFLT account! InterAction does not run if the password for IDCDFLT is changed!
Change the Database Account Password (IDCAPP)
- Choose Administer > Change IDCAPP Password to open the Change IDCAPP Password dialog box.
-
Enter the new password in both the New Password and Confirm Password fields.
Note that InterAction Administrator does not perform any validation on the password – you must enter a valid password for the database platform you are using.
-
Choose OK.
If you change the password after the other applications have been installed, all services and processes will need to be stopped and started for the new password to take effect.