Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329567

Summary: JNDI behaviour causes account lockout
Product: z_Archived Reporter: john mcteague <john.mcteague>
Component: BIRTAssignee: Birt-DataAccess <Birt-DataAccess-inbox>
Status: NEW --- QA Contact:
Severity: minor    
Priority: P3 CC: lchan
Version: 2.6.1   
Target Milestone: Future   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description john mcteague CLA 2010-11-05 13:13:43 EDT 
Build Identifier: 2.5.1

Kind of related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=150132.

If i have a birt template with both jndi and non jndi datasource details configured (the non jndi datasources typically pointing to dev environment) and then run my report on my server where the JNDI resource is available, we get the situation where db account lockouts occur because across dev, uat and prod the same db username is used, but with different passwords obviously.

With the design file trying to get the jndi url first using the username and password, it gets a failed login, then fails over to the jndi url only. Eventually this results in a locked account.

The workaround is to blank out username and password, but then we need to set them back up each time we want to edit the report.

Reproducible: Always
Comment 1 Linda Chan CLA 2010-11-05 18:26:31 EDT 
The recommended way to adjust the connection properties across development and deployment environments is to externalize the property values from the report design.
BIRT provides multiple alternate solutions to externalize property values.

See BIRT forum postings that describe the various solutions. For example,

http://www.eclipse.org/forums/index.php?t=msg&th=199581&start=0&S=65a0d4267f1343aac0a8317abfcd3d7c

http://www.eclipse.org/forums/index.php?t=msg&S=65a0d4267f1343aac0a8317abfcd3d7c&th=171146&goto=636214#msg_636214