Skip to main content

Integration Concept

To start integrating with azuma doa, check out the Gettings Started pages.

Integration concepts:​

Applications​

Applications are used to organize the different products that are integrated with azuma doa. Each Development Tenant can have as many Applications as needed.

Each Application has

  • a name and
  • a short key

and defines a set of

  • clients,
  • roles,
  • permissions and
  • licences.

The short key is important to identify the Application as well as for the definition of Application roles, permissions and scopes. Each Application role/permission/scope needs to be prefixed with the short key (lowercase) to create a unique identifier.

caution

The short key is globally unique and can not be modified after the Application is created.

Roles & Permissions​

Most apps/use cases require a certain set of roles & permissions and licenses. azuma doa allows the definition of those roles & permissions and licenses within an Application.

permission defines an atomic unit identifying an ability to execute a certain functionality. Individual permissions cannot be assigned to a user within azuma doa.

role is used to bundle permissions and is assigned to users. A permission can be used within multiple different roles.

Licenses​

A license authorizes the usage of a certain software / component or function and is assigned to users.