[Building Sakai] Can't Login After Sakai 10.3 Upgrade
Miller, Jeffrey
jeffrey.miller.ctr at usuhs.edu
Sat Jan 10 07:18:06 PST 2015
Thanks Sam, my Github username is jebmiller.
On Thu, Jan 8, 2015 at 12:26 PM, Sam Ottenhoff <ottenhoff at longsight.com>
wrote:
> Thanks Jeb. I believe you are absolutely right. I filed a blocker bug
> here:
>
> https://jira.sakaiproject.org/browse/SAK-28965
>
> And made a pull request here:
> https://github.com/sakaiproject/sakai/pull/25
>
> If you want authorship credit in Github, please let us know your Github
> username.
>
> --Sam
>
> On Thu, Jan 8, 2015 at 9:42 AM, Miller, Jeffrey <
> jeffrey.miller.ctr at usuhs.edu> wrote:
>
>> I was just trying to point out that with Spring 3.2.3-RELEASE the package
>> has changed from org.springframework.security.util.FilterChainProxy to
>> org.springframework.security.web.FilterChainProxy.
>>
>> On Fri, Jan 2, 2015 at 9:58 AM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>>> This was changed in https://jira.sakaiproject.org/browse/SAK-27924
>>>
>>> I don't see why using spring-security-core 3.2.3-RELEASE would cause any
>>> problems, and seems to be the correct version to match with the other
>>> spring libraries now used in Sakai.
>>>
>>> On Fri, Jan 2, 2015 at 9:49 AM, Miller, Jeffrey <
>>> jeffrey.miller.ctr at usuhs.edu> wrote:
>>>
>>>> sakai-10.2/login-tool/tool/pom.xml is using spring version 2.0.4.
>>>> sakai-10.3/login-tool/tool/pom.xml is using ${sakai.spring.version}
>>>> where sakai.spring.version = 3.2.3.RELEASE.
>>>>
>>>> The simple fix is to use spring version 2.0.4.
>>>>
>>>>
>>>> On Tue, Dec 30, 2014 at 4:00 PM, Miller, Jeffrey <
>>>> jeffrey.miller.ctr at usuhs.edu> wrote:
>>>>
>>>>> I had to fix three files:
>>>>>
>>>>> login/login-tool/tool/pom.xml - additional spring security
>>>>> dependencies:
>>>>>
>>>>> <dependency>
>>>>> <groupId>org.springframework.security</groupId>
>>>>> <artifactId>spring-security-config</artifactId>
>>>>> <version>${sakai.spring.version}</version>
>>>>> </dependency>
>>>>>
>>>>> <dependency>
>>>>> <groupId>org.springframework.security</groupId>
>>>>> <artifactId>spring-security-web</artifactId>
>>>>> <version>${sakai.spring.version}</version>
>>>>> </dependency>
>>>>>
>>>>> login/login-tool/tool/src/webapp/WEB-INF/web.xml - change
>>>>> FilterChainProxy class:
>>>>>
>>>>>
>>>>> <!--param-value>org.springframework.security.util.FilterChainProxy</param-value-->
>>>>>
>>>>> <param-value>org.springframework.security.web.FilterChainProxy</param-value>
>>>>>
>>>>> login/login-tool/tool/xlogin-context.xml (goes in sakai.home) - change
>>>>> FilterChainProxy class:
>>>>> <!--bean
>>>>> id="org.springframework.security.util.FilterChainProxy"
>>>>> class="org.springframework.security.util.FilterChainProxy"-->
>>>>> <bean id="org.springframework.security.web.FilterChainProxy"
>>>>> class="org.springframework.security.web.FilterChainProxy">
>>>>>
>>>>> On Tue, Dec 30, 2014 at 12:21 PM, Miller, Jeffrey <
>>>>> jeffrey.miller.ctr at usuhs.edu> wrote:
>>>>>
>>>>>> I did a 'clean' build and deploy after running my cleantomcat.sh
>>>>>> script. Here's an excerpt from localhost.2014-12-30.log:
>>>>>>
>>>>>> Dec 30, 2014 12:12:32 PM org.apache.catalina.core.StandardContext
>>>>>> listenerStart
>>>>>> SEVERE: Exception sending context initialized event to listener
>>>>>> instance of class
>>>>>> org.sakaiproject.login.springframework.SakaiHomeContextLoaderListener
>>>>>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
>>>>>> Configuration problem: Unable to locate Spring NamespaceHandler for XML
>>>>>> schema namespace [http://www.springframework.org/schema/security]
>>>>>> Offending resource: file
>>>>>> [/home/jmiller/apache-tomcat-7.0.54/sakai/xlogin-context.xml]
>>>>>>
>>>>>> at
>>>>>> org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
>>>>>> ...
>>>>>>
>>>>>> On Tue, Dec 30, 2014 at 11:41 AM, Matthew Jones <
>>>>>> matthew at longsight.com> wrote:
>>>>>>
>>>>>>> Google says that the error about "SEVERE: Error listenerStart" is
>>>>>>> generally related to some classpath problem. Did you deploy to a new
>>>>>>> directory or overwrite an existing? Did you clean up duplicate jars in the
>>>>>>> classpath? By default it looks like conf/logging.properties should write
>>>>>>> out some additional info to a file in the logs directory with the localhost
>>>>>>> prefix. (Like localhost.2014-13-03.log) Did you check this file to see if
>>>>>>> there's any hints about what could be going wrong?
>>>>>>>
>>>>>>> On Tue, Dec 30, 2014 at 11:33 AM, Miller, Jeffrey <
>>>>>>> jeffrey.miller.ctr at usuhs.edu> wrote:
>>>>>>>
>>>>>>>> Greetings,
>>>>>>>>
>>>>>>>> I just upgraded from Sakai 10.2 to Sakai 10.3 (Tomcat 7.0.54,
>>>>>>>> Oracle DB, CAS SSO, same local.properties). I'm now experiencing the
>>>>>>>> following:
>>>>>>>>
>>>>>>>> INFO: Deploying web application archive
>>>>>>>> /home/jmiller/apache-tomcat-7.0.54/webapps/sakai-login-tool.war
>>>>>>>> 2014-12-30 11:07:47,241 INFO org.sakaiproject.util.ToolListener -
>>>>>>>> registering tools from resource: /tools/sakai.login.xml
>>>>>>>> Dec 30, 2014 11:07:47 AM org.apache.catalina.core.StandardContext
>>>>>>>> startInternal
>>>>>>>> SEVERE: Error listenerStart
>>>>>>>> Dec 30, 2014 11:07:47 AM org.apache.catalina.core.StandardContext
>>>>>>>> startInternal
>>>>>>>> SEVERE: Context [/sakai-login-tool] startup failed due to previous
>>>>>>>> errors
>>>>>>>> 2014-12-30 11:07:47,257 INFO
>>>>>>>> org.sakaiproject.util.ContextLoaderListener - Destroying Components in
>>>>>>>> xlogin
>>>>>>>>
>>>>>>>> And a stack trace ensues upon login (of course):
>>>>>>>> org.sakaiproject.portal.api.PortalHandlerException:
>>>>>>>> java.lang.NullPointerException
>>>>>>>> at
>>>>>>>> org.sakaiproject.portal.charon.SkinnableCharonPortal.doGet(SkinnableCharonPortal.java:905)
>>>>>>>>
>>>>>>>> Am I missing a new config or property setting somewhere?
>>>>>>>>
>>>>>>>> Any help would be greatly appreciated.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> -jeb
>>>>>>>> --
>>>>>>>> Jeb Miller
>>>>>>>> Programmer Analyst - Sakai, HJF
>>>>>>>> USUHS/ATD
>>>>>>>> 4301 Jones Bridge Road
>>>>>>>> Bethesda, MD 20814-4799
>>>>>>>> 301-319-0442
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> sakai-dev mailing list
>>>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>>>
>>>>>>>> TO UNSUBSCRIBE: send email to
>>>>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>>>>> "unsubscribe"
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jeb Miller
>>>>>> Programmer Analyst - Sakai, HJF
>>>>>> USUHS/ATD
>>>>>> 4301 Jones Bridge Road
>>>>>> Bethesda, MD 20814-4799
>>>>>> 301-319-0442
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jeb Miller
>>>>> Programmer Analyst - Sakai, HJF
>>>>> USUHS/ATD
>>>>> 4301 Jones Bridge Road
>>>>> Bethesda, MD 20814-4799
>>>>> 301-319-0442
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jeb Miller
>>>> Programmer Analyst - Sakai, HJF
>>>> USUHS/ATD
>>>> 4301 Jones Bridge Road
>>>> Bethesda, MD 20814-4799
>>>> 301-319-0442
>>>>
>>>
>>>
>>
>>
>> --
>> Jeb Miller
>> Programmer Analyst - Sakai, HJF
>> USUHS/ATD
>> 4301 Jones Bridge Road
>> Bethesda, MD 20814-4799
>> 301-319-0442
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
--
Jeb Miller
Programmer Analyst - Sakai, HJF
USUHS/ATD
4301 Jones Bridge Road
Bethesda, MD 20814-4799
301-319-0442
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20150110/2ee6f5f3/attachment.html
More information about the sakai-dev
mailing list