You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2012/12/07 11:57:21 UTC

[jira] [Commented] (OAK-497) No LoginModules configured error on Java 7

    [ https://issues.apache.org/jira/browse/OAK-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526312#comment-13526312 ] 

Michael Dürig commented on OAK-497:
-----------------------------------

Sorry for being PITA but this is exactly the same fix I did for OAK-379 [1], and which was reverted [2]. I wonder what changed in the mean while to admit this.

[1] https://fisheye6.atlassian.com/viewrep/jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/security/SecurityProviderImpl.java?r1=1398877&r2=1399192
[2] https://fisheye6.atlassian.com/changelog/jackrabbit?cs=1399273
                
> No LoginModules configured error on Java 7
> ------------------------------------------
>
>                 Key: OAK-497
>                 URL: https://issues.apache.org/jira/browse/OAK-497
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>         Environment: java version "1.7.0_04"
> Java(TM) SE Runtime Environment (build 1.7.0_04-b20)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.6
>
>
> The AuthenticationConfigurationImpl uses Configuration.getConfiguration() to get JAAS configuration when available, and falls back to the default OakConfiguration when not.
> That fallback is currently triggered by a SecurityException thrown from getConfiguration(), which seems to *not* happen on Java 7 where instead just an empty Configuration is returned.
> A better approach might be to check if the returned configuration (if any) contains entries for the specified appName, and to fall back to default configuration if not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira