24d70827b7
1. Definded with properties users (static) are configured using property map (no need of indexes) 2. AuthenticationProvider that authenticates them is always registered (if not needed - don't configure them) 3. UserDetailsService (in case of missing - won't be registered) 4. Spring security user (spring.security.username) will be registered together with other users (if any). If any - it will be system-wide, otherwise tenant-scoped. 5. UserPrincipal renamed to TenantAwareUser in order to match its purpose. 6. Some if its fields are removes as not needed - to be closer to spring security user 7. DefaultRolloutApprovalStrategy now use UserAuthoritiesResolver instead of UserDetailsService as the central point of truth Signed-off-by: Marinov Avgustin <Avgustin.Marinov@bosch.com>
hawkBit Runtime
| Folder | Description |
|---|---|
.sandbox/ |
Content of the hawkBit sandbox installation running on hawkbit.eclipseprojects.io. |
docker/ |
Docker related files, such es Dockerfiles, compose and stack files to quickly start up an hawkBit. |
docker/docker_build/ |
Docker images build related files, such es Dockerfiles and build shell scripts. |
hawkbit-update-server/ |
Spring-Boot application of hawkBit. Monolith containing all services. |
hawkbit-ddi-server/ |
Spring-Boot application of hawkBit DDI server. |
hawkbit-dmf-server/ |
Spring-Boot application of hawkBit DMF server. |
hawkbit-mgmt-server/ |
Spring-Boot application of hawkBit Management server. Provides REST Management API and rollouts / auto assigment processing |
Note: micro service setup requires all services using DB to use same shared DB. So, they don't work with default in memory H2 database. Docker compose with mysql shows an example setup.