Dear All,

I am having an issue CASifying JIRA. Before we are using CAS version 3.05 and 
JIRA version 4.2 and we don't have any problem. Now we upgraded our JIRA to 
version 4.3.4 with java-6-sun-1.6.0.22, MySQL 5.1, Debian Lenny OS. Our 
connection was using LDAP Authentication. When I raise this issue to Atlassian 
they said that it could be some CAS client incompatibility. My CAS Version now 
is 3.4.2 but this was compiled using maven2 war overlay method which I refer to 
this 
link<https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method>.

>From the cas server itself using http://cas-server/cas/login i am able to 
>login successfully using ldap authentication but if I access our JIRA when 
>prompted for username and password upon login I am getting this error:

{code}
2011-08-15 10:23:50,629 http-8090-1 ERROR      
[soulwing.cas.client.DefaultValidatorImpl] error in accessing CAS service:
org.soulwing.cas.client.ServiceAccessException: java.net.SocketException: 
Unexpected end of file from server
        at 
org.soulwing.cas.client.jdom.JdomProtocolHandlerImpl.getJdomDocument(JdomProtocolHandlerImpl.java:96)
        at 
org.soulwing.cas.client.jdom.JdomProtocolHandlerImpl.getResponseElement(JdomProtocolHandlerImpl.java:69)
        at 
org.soulwing.cas.client.jdom.JdomProtocolHandlerImpl.processResult(JdomProtocolHandlerImpl.java:54)
        at 
org.soulwing.cas.client.DefaultValidatorImpl.serviceValidate(DefaultValidatorImpl.java:49)
        at 
org.soulwing.cas.filter.ServiceValidationAuthenticator.authenticate(ServiceValidationAuthenticator.java:65)
        at 
org.soulwing.cas.filter.AbstractValidationFilter.validate(AbstractValidationFilter.java:266)
        at 
org.soulwing.cas.filter.AbstractValidationFilter.doHttpFilter(AbstractValidationFilter.java:206)
        at 
org.soulwing.cas.filter.AbstractValidationFilter.doFilter(AbstractValidationFilter.java:174)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.soulwing.cas.filter.SimpleBypassFilter.doHttpFilter(SimpleBypassFilter.java:116)
        at 
org.soulwing.cas.filter.SimpleBypassFilter.doFilter(SimpleBypassFilter.java:95)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.soulwing.cas.filter.AbstractLogoutFilter.doHttpFilter(AbstractLogoutFilter.java:311)
        at 
org.soulwing.cas.filter.AbstractLogoutFilter.doFilter(AbstractLogoutFilter.java:288)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:554)
        at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
        at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.SocketException: Unexpected end of file from server
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
        at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1200)
        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown 
Source)
        at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown 
Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source)
        at 
org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDExternalSubset(Unknown Source)
        at 
org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown 
Source)
        at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
Source)
        at org.jdom.input.SAXBuilder.build(SAXBuilder.java:453)
        at 
org.soulwing.cas.client.jdom.JdomProtocolHandlerImpl.getJdomDocument(JdomProtocolHandlerImpl.java:90)
        ... 28 more
2011-08-15 10:23:50,630 http-8090-1 ERROR      
[soulwing.cas.client.DefaultValidatorImpl] assuming that ticket 
ST-13-qUGeZG7twYcQSAIbcbfz-cas is stale
{code}

Can you please tell me what is wrong with my configuration? Is there an easy 
way to CASify JIRA and Confluence?

Can anyone please help me?  Thank you.

Kind regards,



BARBOSA Bernard

Senior Administrator, System/Network

MUSIC Group Macao Commercial Offshore Limited (Philippines) ROHQ

IP Phone: 60651 ext 1245

Tel: +63 2 9028200 ext 1245

Email: [email protected]<mailto:[email protected]>

Web: www.music-group.com<http://www.music-group.com> | 
www.behringer.com<http://www.behringer.com> | 
www.bugera-amps.com<http://www.bugera-amps.com>


[Description: http://www.music-group.com/scicons/youtube.jpg] 
youtube.com/behringer  <http://www.youtube.com/behringer> [Description: 
http://www.music-group.com/scicons/facebook.jpg]  facebook.com/behringer 
<http://www.facebook.com/behringer>  [Description: 
http://www.music-group.com/scicons/twitter.jpg]  twitter.com/behringer 
<http://www.twitter.com/behringer>  [Description: 
http://www.music-group.com/scicons/myspace.jpg]  myspace.com/behringer  
<http://www.myspace.com/behringer> [Description: 
http://www.music-group.com/scicons/soundcloud.png]  soundcloud.com/behringer 
<http://www.soundcloud.com/behringer>


:) Build Teamwork   :) Take Ownership   :) Don't Waste Resources   :) Clean 
Workplace = Clean Mind   :) Respect Guidelines and Policies   :) Improve 
Yourself and Help Others   :) Don't Forget to Smile and Say Thank You

This email is intended exclusively for the addressee(s) named above and may 
contain privileged and confidential information. If you are not (among) the 
intended recipient(s), you may not copy, utilize or distribute any of the 
information contained herein. If you have received this email in error, please 
notify us immediately via return email and delete the original from your 
mailbox. Thank you.

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

<<inline: image001.jpg>>

<<inline: image002.jpg>>

<<inline: image003.jpg>>

<<inline: image004.jpg>>

<<inline: image006.png>>

Reply via email to