Hi Marco, We are experience the same issues with the CAS integration as 
well. 

We did put together some instructions on modifying / updating the 
seraph-config.xml and web.xml files, and you can download the .JAR files we 
used 
here: https://bitbucket.org/mbrown_ascend/jira-cas-integration/downloads/. 
Although I'm not sure how to fix those issues other than adding "/*" 
instead of default.jsp in the filter mapping for the CasSingleSignOutFilter, 
CasAuthenticationFilter, and CasValidationFilter. 

By adding /* though, it breaks the Dashboard all over again and the _MSG 
error appear. 

Hope this helps a little, but we are also experiencing the same issue.

Mike

On Thursday, April 27, 2017 at 5:09:59 AM UTC-4, Marco Osorio wrote:
>
> Hello,
> I have a problem with jira + cas authentication. I've followed the setup 
> instructions that come up with two things.
> 1. In the web.xml configuration, if I comment the CasValidationFilter 
> filter, JIRA v7.3.1 starts correctly if errors. When authentic with CAS 
> takes me to the DashBoard but the login widget keeps appearing without 
> content and does not allow me to visualize anything else, as if I was 
> waiting to validate the login.
> 2. If I activate the CasValidationFilter filter, when authenticating with 
> CAS, it generates a double ticket validation error with this trace:
> Org.jasig.cas.client.validation.TicketValidationException:
>              Ticket 'ST-380-eMVDywffQFkJ0W6DYY5f-DVMAPL207' not recognized 
> ....
> The versions of cas-client-core-3.2.1.jar and 
> cas-client-integration-atlassian-3.4.2.jar libraries
> Is there any missing configuration changes to avoid this double ticket 
> validation?
> Thank you
>
> El viernes, 9 de diciembre de 2016, 23:04:05 (UTC+1), Jason Hitt escribió:
>>
>> I've created a pull request for a new Jira7CasAuthenticator at 
>> https://github.com/apereo/java-cas-client/pull/197
>>
>> There is example seraph-config.xml code in the comment.  Using this 
>> authenticator, you do not need any servlet filter updates in web.xml to get 
>> SSO.
>>
>> If you want single sign-out support you should still include those 
>> filters and handlers.
>> If you want transparent SSO at your default URL (instead of seeing the 
>> login page and having to click 'Login'), use the CasAuthenticationFilter i 
>> listed previously, but change the filter mapping from /* to /default.jsp.
>>
>> This configuration is working 100% with JIRA 7 for us on our test server.
>>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/e972f26c-9c62-4dd3-a222-eca6817cf95a%40apereo.org.

Reply via email to