You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org> on 2005/11/22 20:08:51 UTC
[jira] Updated: (GERONIMO-818) Change system-database-plan.xml to specify userid and password on the SystemDatasource and enhance installer to configure it
[ http://issues.apache.org/jira/browse/GERONIMO-818?page=all ]
Matt Hogstrom updated GERONIMO-818:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
> Change system-database-plan.xml to specify userid and password on the SystemDatasource and enhance installer to configure it
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-818
> URL: http://issues.apache.org/jira/browse/GERONIMO-818
> Project: Geronimo
> Type: Improvement
> Components: core
> Versions: 1.0-M4, 1.0-M5
> Reporter: John Sisson
> Assignee: John Sisson
> Fix For: 1.x
>
> If a user creates a derby.properties file in geronimo/var/derby that enables Authentication, e.g.
> #
> #Security settings
> #
> derby.connection.requireAuthentication=true
> derby.authentication.provider=BUILTIN
> #
> # User and password list for Derby BUILTIN authentication provider
> #
> derby.user.geronimo=manager
> derby.user.myapp=myapppswd
> Then this causes problems with the system-database-plan processing.. e.g.
> 12:42:07,277 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: objectName="geronimo.server:J2EEApplication=null,J2EEModule=org/apache/geronimo/SystemDatabase
> ,J2EEServer=geronimo,j2eeType=GBean,name=JDBCNonTransactionalThreadPooledTimer"
> SQL Exception: Connection refused : Invalid authentication.
> Currently the tables created by Geronimo and ActiveMQ are created by default under the APP schema. If we change the system-database-plan to use the userid 'geronimo', then the tables will be created under a schema of the same name. I would prefer that we don't user a userid of system, as it may be confused with Derby's SYS schema.
> We need to allow users to configure authentication in Derby without breaking Geronimo.
> Need to investigate further.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira