Skip to content

openwms/org.openwms.core.uaa

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Purpose

The OpenWMS.org UAA (User Account & Administration) Service deals with the administration of Users like creating new Users, updating properties of existing ones or deleting them. Application permissions are not directly granted to Users explicitly, but to Roles instead. Users are assigned to Roles and application permissions were granted to particular Roles. An administration API for Roles and permissions is especially required for a UI application.

classes

An User has embedded UserDetails, and Emails assigned. However, the password history of the User is managed and compared against new passwords. An User can be assigned to multiple Roles. A Role is a SecurityObject in general and has multiple Grants assigned. A Grant is a permission that can be used in a client application.

Resources

Module Build Status Quality License Maven Central Docker Hub Chat
Image Build status License Maven central Docker pulls Join the chat at https://gitter.im/openwms/org.openwms
Library Build status Quality License Maven central Docker pulls Join the chat at https://gitter.im/openwms/org.openwms

Find more information about the service on the microservice website.

Dependencies

The service is basically a composition of custom libraries. Compared to the opensource version, the ENTERPRISE version contains additional endpoints for the user interface.

mavendeps

Build

Build a runnable fat jar with execution of all unit and in-memory database integrations:

$ mvnw package

Run

After the binary has been built it can be started from command line. No other infrastructure services are required to run this service.

$ java -jar target/openwms-core-uaa-exec.jar

In a distributed Cloud environment the service can itself register on a central discovery service - currently Eureka is supported only. This behavior can be enabled by activating the Spring Profile DISTRIBUTED.

$ java -jar target/openwms-core-uaa-exec.jar --spring.profiles.active=DISTRIBUTED

Now the UAA service is registered at the discovery service at startup and can be looked up by other services by its name uaa-service.

Release

$ mvn deploy -Prelease,gpg

Release Documentation

$ mvn package -DsurefireArgs=-Dspring.profiles.active=ASYNCHRONOUS,TEST
$ mvn site scm-publish:publish-scm