Issue with cas-client-integration-atlassian

[Nicolau Roca]

Good day!

We have a problem regarding cas-client-integration-atlassian, and I kindly write to you hoping that maybe you will be able to help us.

We use Confluence (version 7.13.7, which is last LTS version) integrated with CAS as SSO solution.

We use last version of cas-client-core (version 3.6.4 obtained from https://mvnrepository.com/artifact/org.jasig.cas.client/cas-client-core/3.6.4) and last version of cas-client-integration-atlassian (version 3.5.1 obtained from https://mvnrepository.com/artifact/org.jasig.cas.client/cas-client-integration-atlassian/3.5.1)

However, we have the following problem:
if we use class ConfluenceCasAuthenticator, then the last login date of users is not updated in Confluence
if we use class Confluence35CasAuthenticator, then the last login date of users is correctly updated, but the users receive the following error from Confluence:

Filter execution threw an exception
class org.jasig.cas.client.integration.atlassian.Confluence35CasAuthenticator tried to access protected method 'void com.atlassian.confluence.event.events.security.SecurityEvent.<init>(java.lang.Object, java.lang.String, java.lang.String, java.lang.String, java.lang.String)' (org.jasig.cas.client.integration.atlassian.Confluence35CasAuthenticator and com.atlassian.confluence.event.events.security.SecurityEvent are in unnamed module of loader org.apache.catalina.loader.ParallelWebappClassLoader @7eb4c565)

The Java code of both classes can be found at https://github.com/apereo/java-cas-client/tree/master/cas-client-integration-atlassian/src/main/java/org/jasig/cas/client/integration/atlassian

So, is there any chance to kindly review cas-client-integration-atlassian code to avoid these problems?

Specifically, my guess is that maybe some additional code should be added to class ConfluenceCasAuthenticator in order to update the last login date of users.

We already opened a request to Atlassian regarding this issue, but their conclusion is that the problem is on the SSO plugin side.

Please feel free to send your comments or any additional information you may need regarding this issue, I will be happy to share!

Thank you very much in advance and best regards

Nicolau