Community
Participate
Working Groups
Report Designer copies JDBC parameters, such as username and password, from library to report XML. BIRT Designer 2.6.2: 1. Create a library 2. Add to the libary JDBC Data Source with url, username, password. 3. Create report 4. Add to report Data Source from library 5. Create Data Set from imported Data Source Afetr creating/editing Data Set, connection data properties appears in the report XML. Workaround is to remove these properties manually from XML source. Expected behavior could be either: 1) writing Data Source parameters to report _only_ when editing imported Data Source 2) disabling editing Data Source parameters when imported from library. It is really useful to externalize connection data, when releasing reports as part of software - we won't share our test databases passwords with clients :-) nor store passwords in a project repository.
It's been 2 years since this bug was opened. I actually encountered this same behavior with BIRT 4.2. Any plans for a fix soon?
If connection data properties are user name/password, these properties are defined with data source. Creating/editing data set won't copy properties from the library to the report design. the expected behavior 1 is not right since library can define a data source that can run. behavior 2 is for the user choice. The user can choose not to editor data source connection parameters. BIRT has no plan to externalize connection data yet. To make the password credible, the user can choose implement the encryption helper extension point. Another option is to use property binding. The password can be bound to a report parameter. Check "Edit Data Source" dialog.
I cannot agree, that changing Data Source silently, when I never edited it *explicitly*, is something expected. Problem is present in BIRT 4.3.1 and Oracle data source. I'd expect, that Report Designer should alter only elements I edit. If I touch Data Set, then Data Source should not be changed in any way, since I didn't request to change it. If, instead, I open the Data Source for editing, then it is ok to save local parameters. Only then.
To protect the password , the user can implement the encryption helper extension.
