[jira] [Commented] (OAK-578) Login with null credentials fails

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

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

AFAIU {{OakConfiguration}} is a workaround/temporary solution for missing repository configurations. See also the TODOs in that class. For the time being this class should IMO provide the respective configuration settings for a backward compatible login behaviour. 
                
> Login with null credentials fails
> ---------------------------------
>
>                 Key: OAK-578
>                 URL: https://issues.apache.org/jira/browse/OAK-578
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Michael Dürig
>
> In contrast to Jackrabbit 2, logging in with {{null}} credentials fails:
> {code}
> javax.jcr.LoginException: Login Failure: all modules ignored
> 	at org.apache.jackrabbit.oak.jcr.RepositoryImpl.login(RepositoryImpl.java:128)
> 	at org.apache.jackrabbit.oak.jcr.RepositoryImpl.login(RepositoryImpl.java:154)
> 	at org.apache.jackrabbit.oak.jcr.RepositoryTest.foo(RepositoryTest.java:117)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> 	at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
> 	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:76)
> 	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195)
> 	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> Caused by: javax.security.auth.login.LoginException: Login Failure: all modules ignored
> 	at javax.security.auth.login.LoginContext.invoke(LoginContext.java:921)
> 	at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
> 	at javax.security.auth.login.LoginContext$5.run(LoginContext.java:706)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:703)
> 	at javax.security.auth.login.LoginContext.login(LoginContext.java:575)
> 	at org.apache.jackrabbit.oak.core.ContentRepositoryImpl.login(ContentRepositoryImpl.java:90)
> 	at org.apache.jackrabbit.oak.jcr.RepositoryImpl.login(RepositoryImpl.java:125)
> {code}

--
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