EMQX 6.2.3 introduces scope validation changes

EMQX Enterprise 6.2.3, as detailed in the project's GitHub release notes, introduces stricter scope validation for Dashboard user and API-key endpoints. Mixed privilege scopes (system, user_management, api_key_management, sso_management) combined with restricted scope lists are now rejected, as privilege scopes are administrator-equivalent and cannot be meaningfully restricted. Pre-existing records with mixed scopes will continue to function until the next update, after which operators must separate privilege-only and non-privilege-only scope lists for successful updates.

Operators should review their existing user and API-key configurations for mixed scope lists before upgrading. If such configurations exist, they must be adjusted to comply with the new validation rules to avoid disruptions during the next update. This change aligns with a broader pattern of tightening access control mechanisms across projects, emphasizing the importance of clear privilege boundaries.