You mean I should create a user called "lsc" and have read and write access to lsc.xml for the lsc user ?
Thanks, Rakesh. Thanks, Rakesh. On Wed, Aug 28, 2013 at 11:25 AM, Clément OUDOT <[email protected]>wrote: > > > 2013/8/28 rakesh pothugunta <[email protected]> > >> Hi, >> >> Can anyone provide an example to have the password encrypted when defined >> the source and destination connection parameters. >> >> Your help would be greatly appreciated. >> >> <databaseConnection> >> <name>src-jdbc</name> >> <url>XXXXXXX</url> >> <username>scott</username> >> <password>ENCRYPTED PASSWORD</password> >> <driver>oracle.jdbc.OracleDriver</driver> >> </databaseConnection> >> I have already looked at the below code should be added in the lsc.xml >> filed. How can I create a lsc.key file ? >> >> <security> >> <encryption> >> <keyfile>$LSC_HOME/etc/lsc.key</keyfile> >> <algorithm>AES</algorithm> >> <strength>128</strength> >> </encryption> >> </security> >> >> >> > The encryption API is designed to be used in datasets, not for the > configuration properties. The password should be in clear in lsc.xml, but > you have to restrict the access to this file to the lsc program. > > Clément. >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
