You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2009/10/19 15:07:31 UTC
[jira] Resolved: (JCR-2358) Prefer JAAS configuration if present
[ https://issues.apache.org/jira/browse/JCR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-2358.
-----------------------------------
Resolution: Won't Fix
It seems the majority is in favour of keeping it the way it is right now. Resolving as WONTFIX.
> Prefer JAAS configuration if present
> ------------------------------------
>
> Key: JCR-2358
> URL: https://issues.apache.org/jira/browse/JCR-2358
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 1.6.0
> Reporter: Marcel Reutegger
> Priority: Minor
>
> Contrary to JavaDoc the AuthContextProvider prefers the local configuration in repository.xml. When the class was first introduced in 1.5, the implementation did what was documented, but then JCR-1977 was reported. I think we shouldn't have fixed it that way. Prefering JAAS over the local configuration makes sense IMO and works well if Configuration.getAppConfigurationEntry() is correctly implemented and behaves as specified/expected.
> I suggest we revert to the 1.5 preference sequence and introduce a parameter that instructs the AuthContextProvider to ignore the JAAS configuration (as a workaround for the buggy application servers).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.