[MAGNOLIA-2572] When enabling JAAS realm in login-config.xml context returns 404 Created: 22/Jan/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: security
Affects Version/s: 3.6.2, 3.6.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Ian Johannesen Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: java6, jboss5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MacOS X 10.5.6 using JDK 6.0 (build 1.6.0_07-b06-57, mixed mode) and Jboss AS 5.0.0.GA


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When the following sniplet isn't in the login-config.xml I'm rightfully prompted with the login box when trying to access the context which Magnolia is running under. However when I put in the following sniplet I get a 404 returned even on /.magnolia/. I haven't been able to debug it further as the 4.0 milestones (empty webapp) doesn't want to even startup under Jboss AS 5.0.0.GA.

        <!--
    magnolia JAAS login modules
    -->
    <application-policy name="magnolia">
       <authentication>
          <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthenticationModule"
             flag = "requisite" />
          <login-module code="info.magnolia.jaas.sp.jcr.JCRAuthorizationModule"
             flag = "required" />
       </authentication>
    </application-policy>

    <!--
    jackrabbit JAAS login modules
    -->
    <application-policy name="Jackrabbit">
       <authentication>
          <login-module code="org.apache.jackrabbit.core.security.SimpleLoginModule"
             flag = "required" />
       </authentication>
    </application-policy>


 Comments   
Comment by Magnolia International [ 23/Jan/09 ]

Hi Ian,

I can't reply to your direct question, but i have two other "side-questions" which hitch me a little:

I haven't been able to debug it further as the 4.0 milestones (empty webapp) doesn't want to even startup under Jboss AS 5.0.0.GA.

  1. Could you elaborate on how it doesn't startup ? (haven't tried myself on this specific version with jdk6, will do right away)
  2. Why does 4.0 not starting block you from debugging a bug on 3.6.x ? There are tags on svn for all releases, and source-jars are also available.

I don't mean to bash at your question, just hoping to clarify some misunderstanding, and possible help one way of the other.

Cheers,
-g

Comment by Magnolia International [ 23/Jan/09 ]

Ian, indeed, I wasn't able to deploy 4.0 snapshots or m2 on jboss5.0 - were you able to deploy a 3.6.3 in there, with the default configuration ?

Comment by Ian Johannesen [ 23/Jan/09 ]

Hi,

Actually the 3.6.3 empty webapp does exactly the same as 4.0-m2 on my Jboss AS 5.0.0.GA.

Sorry for not being very clear, but I get the following error under startup of the webapp:

07:14:05,417 INFO  [STDOUT] INFO   info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(registerNodeTypes:353) 23.01.2009 07:14:05  registering nodetype {http://www.magnolia.info/jcr/mgnl}group
07:14:08,588 INFO  [STDOUT] INFO   info.magnolia.cms.beans.config.ContentRepository ContentRepository.java(init:200) 23.01.2009 07:14:08  System : JCR loaded
07:14:08,684 ERROR [[/testsite]] Exception sending context initialized event to listener instance of class info.magnolia.cms.servlets.MgnlServletContextListener
java.lang.RuntimeException: javax.jcr.PathNotFoundException: modules
	at info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:346)
	at info.magnolia.module.ui.ModuleManagerWebUI.onStartup(ModuleManagerWebUI.java:80)
	at info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:138)
	at info.magnolia.cms.beans.config.ConfigLoader.<init>(ConfigLoader.java:107)
	at info.magnolia.cms.servlets.MgnlServletContextListener$1.exec(MgnlServletContextListener.java:178)
	at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:411)
	at info.magnolia.cms.servlets.MgnlServletContextListener.startServer(MgnlServletContextListener.java:176)
	at info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:172)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393)
	at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367)
	at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146)
	at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460)
	at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
	at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
	at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
	at $Proxy36.start(Unknown Source)

However my custom built 3.6.2-SNAPSHOT with our custom modules in it does start-up. I don't know if it's because it's using Oracle for JCR persistence storage. I will try to go down this road to debug it further later today. As per question number two I simply compared our custom 3.6.2-SNAPSHOT to an upgraded version to 3.6.3 and tried an empty webapp from sourceforge of 4.0-m2

/Ian

Comment by Magnolia International [ 09/Sep/09 ]

Late reply, but the above stacktrace might be an indicator that your repository couldn't be started; there should be error/warnings above that, in the logs.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:38:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.