Skip to main content

​
6.2.1 to 6.2.2

​
Support for 6.0.x and 6.0.x-sb3 Atoti Servers removed

Atoti Limits has removed support for connecting to Atoti Server 6.0.x and 6.0.x-sb3, which have reached end of support. This affects anyone using limits-auto-config-60 or limits-auto-config-60-sb3. The connected Atoti Server instance must be upgraded to 6.1.x or 6.2.x — see the Atoti Server migration notes for that upgrade. After upgrading the connected server, switch the Maven dependency to the matching artifact:
  • For Atoti Server 6.1.x, use limits-auto-config-61.
  • For Atoti Server 6.2.x, use limits-auto-config-62.
For the current list of supported artifacts, see the compatibility matrix.

​
limits-common module removed

The limits-common Maven module no longer exists. Its classes keep their packages (com.activeviam.limits.core.shared.*) and now ship with the module that uses them:
  • limits-activeviam on the Atoti Limits server,
  • limits-integration-common on a connected Atoti Server (pulled in by limits-auto-config-<version>).
No project is expected to depend on limits-common directly, as it was already a transitive dependency of both. If your pom.xml declares it anyway, remove the dependency: the classes are available through limits-activeviam or limits-auto-config-<version>. Classes you override keep their fully qualified names, so no import changes are needed.

​
6.2.0 to 6.2.1

No migration necessary.

​
6.1.23 to 6.2.0

Atoti Limits now requires Java 25. Update your project to build and run with Java 25. Spring Security Kerberos is now published in the org.springframework.security group, and released with Spring Security itself. If your project declares a spring-security-kerberos-* dependency of its own, for instance to set up Kerberos machine-to-machine authentication, change its groupId to org.springframework.security and drop its version, which Spring Boot’s dependency management now provides. The 2.x releases of the retired org.springframework.security.kerberos group are compiled against org.springframework.security.crypto.codec.Base64, a class Spring Security 7 removed, so authenticating a request with them fails at runtime with java.lang.ClassNotFoundException. No code migration is necessary.