Files

Avgustin Marinov 24d70827b7 Improve hawkBit user management (#1666 )

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>

2024-02-26 16:56:37 +02:00

src

Improve hawkBit user management (#1666 )

2024-02-26 16:56:37 +02:00

pom.xml

[#1383 ] Spring Boot 3 migration Step 2 (#1559 )

2024-01-20 15:57:17 +02:00

README.md

Mark new micro-service setup as experimental (#1502 )

2023-12-07 15:15:12 +02:00

README.md

hawkBit Management Server (EXPERIMENTAL!)

The hawkBit Management Server is a standalone spring-boot application with an embedded servlet container. It should be started with at least one (or both) of the device interface servers - hawkbit-ddi-server or/and hawkbit-dmf-server.

On your own workstation

Run

java -jar hawkbit-runtime/hawkbit-mgmt-server/target/hawkbit-mgmt-server-*-SNAPSHOT.jar

(Note: you have to add the JDBC driver also to your class path if you intend to use another database than H2.)

Or:

run org.eclipse.hawkbit.app.mgmt.MgmtServerStart

Usage

The Management API can be accessed via http://localhost:8080/rest/v1 The root url http://localhost:8080 will redirect directly to the Swagger Management UI

Clustering (Experimental!!!)

The micro-service instances are configured to communicate via Spring Cloud Bus. You could run multiple instances of any micro-service but hawkbit-mgmt-server. Management server run some schedulers which shall not run simultaneously - e.g. auto assignment checker and rollouts executor. To run multiple management server instances you shall do some extensions of hawkbit to ensure that they wont run schedulers simultaneously or you shall configure all instances but one to do not run schedulers!

Optional Protostuff for Sprign cloud bus

The micro-service instances are configured to communicate via Spring Cloud Bus. Optionally, you could use Protostuff based message payload serialization for improved performance.

Note: If Protostuff is enabled it shall be enabled on all microservices!

Add/Uncomment to/in your application.properties :

spring.cloud.stream.bindings.springCloudBusInput.content-type=application/binary+protostuff
spring.cloud.stream.bindings.springCloudBusOutput.content-type=application/binary+protostuff

Add to your pom.xml :

<dependency>
  <groupId>io.protostuff</groupId>
  <artifactId>protostuff-core</artifactId>
</dependency>
<dependency>
  <groupId>io.protostuff</groupId>
  <artifactId>protostuff-runtime</artifactId>
</dependency>