Issue #406 has been updated by Sébastien Bahloul.
Hi Waldemar, Currently, the original generated path is the configuration directory. Then you can move it anywhere you want and specify the path inside the configuration. Someone would have said that it's not a bug it's a feature :) I'll fix that so that the path, including the first time the file is generated is the path specified if any, and the configuration directory if not. Regards, ---------------------------------------- Bug #406: Key generation is currently broken http://tools.lsc-project.org/issues/406 Author: Waldemar Schlackow Status: Feedback Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 2.0.x branch Problem in version: 2.0 Hi, we've just started using your project, which does an excellent job! I wanted to take it to the next level to use the encryption/decryption routines you provide, but when trying to generate a key, I get a NullPointerException. I suspect that when the commit 1436 went in for the new configuration scheme, the variable "algo" was overlooked which is now always Null when KeyGenerator.getInstance is called. I suspect the change that is needed is change KeyGenerator.getInstance(algo, securityProvider.getName()); to KeyGenerator.getInstance(securityProvider.getAlgorithm(), securityProvider.getName()); in utils/security/SymmetricEncryption.java The commit I mean is below. http://tools.lsc-project.org/projects/lsc/repository/diff/lsc/trunk/src/main/java/org/lsc/utils/security/SymmetricEncryption.java?rev=1436&rev_to=1401 Many thanks for all your work on this! -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
