PowerDesigner encrypts repository passwords in the repository database and encrypts the database password for repository definitions stored in the registry. However, it does not encrypt repository passwords in the registry, nor database passwords entered in connection profiles. Consequently, to improve security, you should avoid storing database passwords in connection profiles and not enter your repository password in repository definitions (though you can securely store the database password in repository definitions).
PowerDesigner supports encryption of both passwords and data for direct connections to a repository or other database using most of the supported DBMSs via one or more of native, ODBC, and JDBC connection profiles. The following table provides information and examples for encrypting passwords and data with each type of connection:
| Type | Encryption |
|---|---|
| Native | Password and data encryption can generally be enabled with connection parameters. For example, the password for Sybase Adaptive Server Enterprise is encrypted by default, and you can enable data encryption by setting the Sec_Confidential connection parameter to 1. |
| ODBC | Password and data encryption can generally be enabled in the ODBC Configuration dialog. For example, to encrypt the password for Sybase SQL Anywhere, select the Encrypt password option on the Login tab, and to encrypt data, select an encryption method on the Network tab. |
| JDBC | It is not possible to control password and data encryption through the PowerDesigner connection profile interface, but you may be able to enable encryption directly in your database client. |
For more information about using PowerDesigner connection profiles, see Core Features Guide > The PowerDesigner Interface > Getting Started > Connecting to a Database. For detailed information about encryption and other parameters for your database, see your DBMS documentation.