-
Terminally Deprecated ElementsElementDescriptionRoles and permissions should only be added to authRoles and permissions should only be added to authDeprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)
-
Deprecated InterfacesInterfaceDescriptionDeprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)since 1.7.0. Roles and permissions are managed in auth.since 1.7.0. Roles and permissions are managed in auth.Since 1.7.0. Role/permissions management moved to authSince 1.7.0. Role/permissions management moved to authsince 1.7.0. Roles and permissions are managed in auth.since 1.7.0. Roles and permissions are managed in auth.
-
Deprecated ClassesClassDescriptionRoles and permissions should only be added to authRoles and permissions should only be added to authDeprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)Deprecated in favor of liquibase insert pattern (see adminuser.starter.required.data.changelog.xml)since 1.7.0. Permissions are managed in Auth.since 1.7.0. Roles are managed in auth.since 1.7.0. Roles and permissions are managed in auth.since 1.7.0. Roles and permissions are managed in auth.since 1.7.0. Roles and permissions are managed in auth. Use
AuthProvider
-
Deprecated MethodsMethodDescriptionin favor of
AdminUser.tenantAccessin favor ofAdminUser.tenantAccessSince 1.7.0. Name is no longer required, thus validating that a permission has a name is no longer necessary. UseValidationSupport.validateAllPermissionsNonNullAndHaveId(Collection, Errors, String, String, String)instead.Since 1.7.0. Name is no longer required, thus validating a role has a name serves no purpose. Instead, useValidationSupport.validateAllRolesNonNullAndHaveId(Collection, Errors, String, String, String)in favor ofJpaAdminUser.tenantAccessin favor ofJpaAdminUser.tenantAccesssince 1.7.0.