It's not usable feature, and is error prone - someone could left anonymous enabled by mistake
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>
* it's not needed for dmf
* also made optional when not needed (e.g. some JpaArtifactManagement)
_release_notes_
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>
as it is controller only related
* DmfTenantSecurityToken renamed to ControllerSecurityToken - as it is such
* hawkbit.security classes from http-security-internal moved to hawkbit.security.controller - as they are such and it is bad practice to have same package in multiple modules
_release_notes_
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>
* SecurityManagedConfiguration is moved to hawkbit-rest-core with commons for mgmt and ddi only
* Configurations for DDI and Management API are moved to respective starters
* hawkbit-http-security is removed - DosFilter (as common) is moved in hawkbit-rest-security, rest to the ddi starter as used only there
* some classes are moved into different packages - it is a bad practice to have same packet into multiple artifacts
_release_notes_
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>