[
https://issues.apache.org/jira/browse/JCR-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated JCR-1562:
--------------------------------
Attachment: bundleDbNoDefaultUserPassword.txt
This patch removes the default user name and password for Oracle, H2, and Derby.
This will always work in Derby as Derby doesn't check user names and passwords
by default.
For Oracle and H2 the problem is backward compatibility: if user name and
password was not configured in previous installations, the old default values
(sa for H2, crx for Oracle) were used. For Oracle, a user name and password is
required in any case. I think this is a problem, but the best way to solve it
is (in my view) to document this change in the release notes.
If nobody objects, I will commit this change in a few days.
> JNDI data sources with various PersistenceManager: wrong default values
> -----------------------------------------------------------------------
>
> Key: JCR-1562
> URL: https://issues.apache.org/jira/browse/JCR-1562
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: core 1.4.2
> Reporter: Sven Rieckhoff
> Attachments: bundleDbNoDefaultUserPassword.txt
>
>
> With JCR-1305 Jackrabbit supports creating a connection throug a JNDI
> Datasource and without configuring user and password. This works for some but
> not all provided PersistenceManagers. Some of them - like the Oracle-specific
> BundleDBPersistenceManager - sets default values for user and password if
> none are provided in the jackrabbit config. This way its impossible to use
> such PersistenceManagers with the plain JNDI DS.
> This concerns the following BundleDbPersistenceManagers:
> OraclePersistenceManager, DerbyPersistenceManager, H2PersistenceManager.
> There also might be other PMs (perhaps some special
> SimpleDbPersistenceManagers) with similar behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
