![]() ![]() This can be done on the SQL Server side or on the CPM side by adding Encrypt=Yes to the connection string. When using the connection methods described above, it is recommended to secure the connection.Įnforce encryption of the connection. The following example displays a valid connection string on a Microsoft SQL Server: ■ĭriver= Server=%ADDRESS% Database=%DATABASE% Uid=%USER% Pwd=%OLDPASSWORD% 2.Ĭreate a temporary DSN and use the testing options in the DSN to test the connection between the CPM machine and the database server. The password of the user who will replace the invalid password with the new password. The name of the user who will replace the invalid password with the new password. The port used by the CPM to access the remote machine. Password Object properties or, if not defined there, from the ExtraInfo section of the platform. ![]() The instance name is case-sensitive and must be specified exactly as it appears. If there are several instances on the same machine, specify the instance as part of the address as follows: The address of the database server where the password is used. Reconcile account password object properties This is either the current password or the password of the reconciliation account. The plugin automatically detects the password to use for logon. The password that the plugin uses for logon. ![]() These variables will be replaced during run time with the appropriate values: The Connection String template may contain any number of the following variables enclosed with ‘%’ (percentage) sign. This parameter is required if the DSN parameter is not supplied either at policy level or password level, indicating that the connection method is DSN‑Less.įor more details about platform parameters, refer to the Privileged Access Security Reference Guide. The Connection String that will be used to connect to the database through ODBC. In the Additional Policy Settings section of the platform, check the values of the following required parameters: Recommended: Secure the connection with SSL/TLS.Ĭonnect to the Remote Database with a Connection String (DSN-less) 1. Make sure that the DSN is a system DSN and not a User DSN. Use the testing option in the DSN to test the connection between the CPM machine and the database server. Create a System DSN for each database in the CPM machine.This plugin supports the following connection methods to connect to remote databases: ■ In the Platform Management page, make sure that the following target account platform is displayed: ■ If the machine does not support this version of ODBC, download the latest MDAC_typ.exe from the Microsoft downloads site. The machine that runs the CPM must support ODBC, version 2.7 and higher. If this driver not installed you can download it from Microsoft downloads web site. ![]() Make sure that a Microsoft SQL Server ODBC driver is installed on the machine that runs the CPM. The following driver is required on the CPM machine: ■ The CPM supports remote password management on a Microsoft SQL Server on the following platforms: ■ Automatic password management is supported on Microsoft SQL Server accounts on IPv4 and IPv6. ![]()
0 Comments
Leave a Reply. |