Community
Participate
Working Groups
Build Identifier: 2.5.2 Implementing an encryption algorithm in the EncryptionHelper results in database access failure, while simply echoing the plaintext results in success. During report processing, the following two lines of code seem to contradict each other, and appear to result in double-encryption of the password: ReportDesignSerializer.localizePropertyValues(DesignElement, DesignElement): value = EncryptionUtil.encrypt( propDefn, encryption, value ); newElement.setProperty( propDefn, value ); - and - ModuleWriter.writeProperty(DesignElement, String, String, Boolean): // getLocalProperty will return decrypted value, so encrypt it here xml = (String) EncryptionUtil.encrypt( propDefn, encryptionID, xml ); Reproducible: Always Steps to Reproduce: 1. Create a custom EncryptionHelper plugin. 2. Utilize the EncryptionHelper during report processing.
This was happening due to differences between the formatting of output from decryption/encryption methods within the host software.
Test with extended encryptionable property. All cases work right including parser, changing property value by command, clone and document generating. Can not reproduce. Maybe, user behavior about EncryptionHelper is wrong. As expected, value passed to PropertyHandle::setValue(String) must be orginal non-encrypted value, for example, if you want to set password to "1234" then String "1234" must be passed to handle method rather than encrypted string. In another point, the value returned by PropertyHandle::getValue/getStringValue will be non-encrypted value like "1234".
It works in my test.
