The Casdoor authentication runtime plugin and Spring Boot starter are no longer built or shipped by the main ShenYu repository. Existing deployments that use Casdoor should add the external plugin-store starter:
<dependency> <groupId>org.apache.shenyu</groupId> <artifactId>shenyu-spring-boot-starter-plugin-casdoor</artifactId> <version>2.7.1-SNAPSHOT</version> </dependency>
The external plugin keeps the same plugin name, order, plugin-data fields, callback parameters, and downstream identity headers (name, id, and organization) used by the former in-tree implementation. Certificates and secrets remain deployment-owned configuration and must not be committed to source control.
The main repository keeps PluginEnum.CASDOOR as a stable compatibility contract for the external plugin and existing admin data during the supported cutover window. The main repository no longer publishes the Casdoor runtime artifact or includes the Casdoor SDK in the default bootstrap distribution.
Rollback during the cutover window is a dependency-only change: remove the external starter and return to a ShenYu build that still shipped the in-tree Casdoor starter. Existing plugin data keeps the same plugin name and configuration schema.