kranthi created FEDIZ-33:
----------------------------
Summary: Can CXF Fediz IDP & RP run with Tomcat 5.5.28 version ?
Key: FEDIZ-33
URL: https://issues.apache.org/jira/browse/FEDIZ-33
Project: CXF-Fediz
Issue Type: Question
Components: Examples, IDP, Plugin
Affects Versions: 1.0.1
Environment: Server version: Apache Tomcat/5.5.28
OS Name: Windows XP
Architecture: x86
Reporter: kranthi
Fix For: 1.0.1
As per the Apache CXF Fediz( Tomcat 7) example, I have configured IDP & RP and
also able to run suceessfully.
The issue when iam trying to replace the tomcat of RP with 5.5.28 version Iam
getting the below error.
I want one clarification, does this federation supports Tomcat 5.5.28 version ?
15:21:44,419 WARN [FormAuthenticator] Unexpected error forwarding to login
page
java.lang.NullPointerException
at
org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:316)
at
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:244)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
at
org.apache.cxf.fediz.tomcat.FederationAuthenticator.invoke(FederationAuthenticator.java:235)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Unknown Source)
--
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
