[
https://issues.apache.org/jira/browse/OAK-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532312#comment-13532312
]
angela commented on OAK-497:
----------------------------
> Once we address the OAK-17 TODO in OakConfiguration and get rid of that class
> there will
> be no need for the extra logic to detect whether a JAAS configuration is
> present or not.
right... for the time being i just added a commented to the code explaining why
it
does the extra check for the missing config.
> 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
