Permissions

In order to be able to guarantee the authorisations within a system, there are strict specifications for the structure of the authorisation

The authorisations are made up as follows.

Scope

The scope describes what an authorisation refers to. The scope type exists to draw a clear boundary between user and realm authorisations. It is also required to manage the permissions within the system and to set the values

Valid values here are: 0(user) or 1(realm)

Action

The action refers to what is to be changed or whether only reading is to take place. By setting the authorization, reading can be enabled while writing is blocked.

Valid values here are: 0(read), 1(write), 2(update) and 3(delete)

Type of authorisation

The authorization type can be used to set whether the operation refers to an object or a process. It is therefore possible to accept the read for an object and then block access to the underlying children.

Valid values here are: 0(object), 1(method/action)

Name of the permission

The name of the authorization is freely selectable. Nevertheless, it makes sense to choose the names of the authorizations in such a way that a clear pattern is recognizable or assignable

Example

An example of an exclusive write authorization to update a realm name could be:

Authorization to perform the operation

1::2::1::realm.update

To change the field of the object, the following authorization is required

1::2::0::realm.name

Application properties

The application.properties file in Spring Boot is used to configure various settings of the application, such as environment-specific configurations, external services, and application behavior. It allows developers to externalize configuration values, enabling easier changes without modifying the application's source code.

Key points

It stores key-value pairs for configuring the application's behavior. Supports different environments by loading environment-specific configuration files. Configuration values can be overridden at runtime by passing them as environment variables, allowing flexibility in deployment.

This makes it possible to adjust configurations based on the runtime environment without changing the file itself.

Configuration Parameters

The environmental variables of the individual services are listed and briefly described in the following points.

Properties