[jira] [Updated] (GERONIMO-5689) User-defined derby connection user name and password should be honored when enabling derby authentication
[ https://issues.apache.org/jira/browse/GERONIMO-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5689: -- Fix Version/s: 2.1.8 > User-defined derby connection user name and password should be honored when > enabling derby authentication > - > > Key: GERONIMO-5689 > URL: https://issues.apache.org/jira/browse/GERONIMO-5689 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.1.7, 2.2.1 > Environment: ubuntu 10.04.1 LTS > sun java 1.5.0_22 >Reporter: Forrest Xia >Assignee: Chi Runhua >Priority: Minor > Fix For: 2.1.8 > > Attachments: bank-ear-2.1.1.4.ear > > > Consider this scenario: > 1. User firstly disables derby authentication, then start the server and > deploy an application which is using embedded derby database. The datasource > deployment plan is like this: > > > > > javax.sql.DataSource > > BankPool >name="Driver">org.apache.derby.jdbc.EmbeddedDriver >name="UserName">app >name="Password">app >name="ConnectionURL">jdbc:derby:BankDB;create=true > > > > 10 > 0 > > > > > > > > In the plan, user specifies an username and password. > 2. Shutdown the server, enable derby authentication, and start the server > again > 3. Now the server cannot start successfullly, because this exception: > Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car > 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User > authentication failure (userName userPassword databaseName): app app BankDB > 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for handle: nullManagedConnectionInfo: > org.apache.geronimo.connector.outbound.ManagedConnectionInfo@123288b. mc: > null] > javax.resource.spi.ResourceAllocationException: Unable to obtain physical > connection to jdbc:derby:BankDB;create=true > ... > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to > start due to the following reasons: > The service > J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit > did not start because Connection authentication failure occurred. Reason: > Invalid authentication.. > I think this exception may cause by derby user is hard-coded in code to > acquire server connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-5689) User-defined derby connection user name and password should be honored when enabling derby authentication
[ https://issues.apache.org/jira/browse/GERONIMO-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-5689: -- Summary: User-defined derby connection user name and password should be honored when enabling derby authentication (was: Derby connection failed when enabled derby system level authentication) > User-defined derby connection user name and password should be honored when > enabling derby authentication > - > > Key: GERONIMO-5689 > URL: https://issues.apache.org/jira/browse/GERONIMO-5689 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.1.7, 2.2.1 > Environment: ubuntu 10.04.1 LTS > sun java 1.5.0_22 >Reporter: Forrest Xia >Priority: Minor > Attachments: bank-ear-2.1.1.4.ear > > > Consider this scenario: > 1. User firstly disables derby authentication, then start the server and > deploy an application which is using embedded derby database. The datasource > deployment plan is like this: > > > > > javax.sql.DataSource > > BankPool >name="Driver">org.apache.derby.jdbc.EmbeddedDriver >name="UserName">app >name="Password">app >name="ConnectionURL">jdbc:derby:BankDB;create=true > > > > 10 > 0 > > > > > > > > In the plan, user specifies an username and password. > 2. Shutdown the server, enable derby authentication, and start the server > again > 3. Now the server cannot start successfullly, because this exception: > Module 69/69 org.apache.geronimo.samples/bank-ear/2.1.1.4/car > 2010-11-15 15:12:25,224 WARN [DerbyUserAuthenticator] User > authentication failure (userName userPassword databaseName): app app BankDB > 2010-11-15 15:12:25,240 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for handle: nullManagedConnectionInfo: > org.apache.geronimo.connector.outbound.managedconnectioni...@123288b. mc: > null] > javax.resource.spi.ResourceAllocationException: Unable to obtain physical > connection to jdbc:derby:BankDB;create=true > ... > Caused by: org.apache.geronimo.gbean.InvalidConfigurationException: > Configuration org.apache.geronimo.samples/bank-ear/2.1.1.4/car failed to > start due to the following reasons: > The service > J2EEApplication=org.apache.geronimo.samples/bank-ear/2.1.1.4/car,j2eeType=GBean,name=BankDBInit > did not start because Connection authentication failure occurred. Reason: > Invalid authentication.. > I think this exception may cause by derby user is hard-coded in code to > acquire server connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
