Crowd 7.0 EAP06 is now available (last 7.0 EAP)

Crowd Development
,
1

We’ve just released the EAP 06 of Crowd 7.0 - last EAP version before 7.0 release, so you can get familiar with the upcoming changes.

Highlights

  • Google Apps Connector support removal – With Crowd 7.0, we’re removing support for Google Apps Connector. The functionality is blocked by default.

Downloads and documentation

For details, check out the documentation on how to prepare for Crowd 7.0.

Share your feedback

If there’s anything we can provide that will make it easier for you to understand and plan for the changes, let us know by commenting below this post.

Happy testing,
The Crowd Team

2

Hi Team,

We are currently facing a critical blocker during the migration of our SAML and OAuth SSO plugin for Crowd to version 7.0.0-EAP03.

As part of the migration process, we have updated our implementation to replace the deprecated class com.atlassian.crowd.manager.TokenAuthenticationManager with the new com.atlassian.crowd.service.authentication.CrowdApplicationAuthenticationService, as recommended.

However, we are encountering severe OSGi-related access issues, specifically:

  • com.atlassian.crowd.service.authentication.CrowdApplicationAuthenticationService and other classes under com.atlassian.crowd.service are inaccessible from within the plugin due to OSGi restrictions (e.g., ClassNotFoundException, package access violations).
  • Similar issues are observed with other critical components required for our SSO functionality:
  • com.atlassian.crowd.manager.authentication.TokenAuthenticationManager
  • com.atlassian.crowd.service.client.CrowdClient
  • com.atlassian.crowd.integration.http.CrowdHttpAuthenticator

This is completely blocking our ability to proceed with the migration, as these APIs are essential to enabling secure and seamless SSO into Atlassian products via Crowd.

Given that our plugin is used by multiple enterprise customers, including those in large-scale production environments, the inability to support Crowd 7.0 due to OSGi restrictions has serious implications:

We appreciate your immediate attention to this matter and look forward to your direction so we can continue supporting Crowd 7.0 in a secure and compatible manner.

Thanks,

3

Hi Lokesh,

Thank you for the feedback!

We just released an on-demand EAP 05 version - with the com.atlassian.crowd.service.authentication.CrowdApplicationAuthenticationService class publicly exposed.

We believe this should allow you to use authentication functionality in your plugin.

Best regards,
The Crowd Team

4

Hi Team,

Thank you for sharing the Crowd 7.0.0-EAP05 release.

While testing our Crowd plugin against this version, we encountered the following issue

Caused by: java.lang.NoClassDefFoundError: com/atlassian/crowd/service/authentication/CrowdApplicationAuthenticationService
...
Caused by: java.lang.ClassNotFoundException: com.atlassian.crowd.service.authentication.CrowdApplicationAuthenticationService not found

It appears that CrowdApplicationAuthenticationService is still not available for OSGI export.

Also, in our use case, we need to authenticate users in the context of a specific application (not necessarily the “crowd” application), and the currently available authenticate() method in CrowdApplicationAuthenticationService appears to enforce authentication only for the “crowd” application itself, which is generally used by Crowd Admin, not by end users.

We also couldn’t find a suitable replacement for the previously available authenticateUserWithoutValidatingPassword method in com.atlassian.crowd.manager.authentication.TokenAuthenticationManager.

Could you please confirm:

  1. Whether CrowdApplicationAuthenticationService (or similar) will be re-exported in the final 7.0 release?

  2. If not, is there an updated approach for application-scoped authentication that doesn’t rely on the Crowd application’s access rules?

We’d appreciate guidance on how to handle application-specific tokens or SAML-based authentication in 7.0+.

Thanks,

Lokesh

2 Likes
5

Hello Lokesh,

Another on-demand EAP version has been published: Crowd 7.0.0 EAP 06

The following Java API should be available for usage in your plugin:

  • CrowdApplicationAuthenticationService
  • ApplicationAuthenticationService - a new interface which allows authentication to non-Crowd applications

Best regards,
The Crowd Team

6

Hi Pawel,

Thank you for the update and for accommodating our request.

We’ve tested Crowd 7.0.0 EAP 06, and everything appears to be working as expected. We’ll continue our validation to ensure full compatibility with Crowd v7 and will reach out if we encounter any issues or need further assistance.

Appreciate your support throughout this process.

Thanks,

Lokesh

1 Like