Documentation
Utilisateur de l’application

General Information About Application Users

The application user is a user which is used by applications to interact with the web services.

The main difference to a human user is that the application user can authenticate without a password. The application user has to sign each request sent to the web service with a pre-shared secret. For details about how to sign those request, please take a look at the corresponding documentation about the web service authentication.

Each application can have exactly two such pre-shared secrets. This allows to change/replace the secret without downtime. E.g. a new secret can be generated and some time later the secret can be updated in the client application. However, in the mean time, the web service will accept requests signed with the old secret.

Roles and Application Users

Application users have roles. Each role grants different permissions to the user. When creating and assigning roles you have to keep in mind that each role is context specific. There are access rights that are bound to the context of a space or an account. You can assign the role only in such a context.

Manage Authentication Key

You can generate new authentication key in the managing application user view in case you lost the old key or when you want to replace it. After the migration is finished you can deactivate the old key. This allows you to use different key versions at the same time.

États
  • Créer
    Le statut Create indique que le type Utilisateur de l’application est en cours de création.
  • Actif
    Le statut actif signifie que l’entrée du type «Utilisateur de l’application» est active et qu’elle peut être utilisée.
  • Inactif
    Le statut Inactif montre que l’entrée de type Utilisateur de l’application est inactive et qu’elle n’est peut-être pas utilisée.
  • En cours de suppression
    Le statut deleting indique que l’entrée du type Utilisateur de l’application est en cours de suppression.
  • Supprimé
    Le statut supprimé marque l’entrée pour la suppression de la base de données.
Propriétés
  • Account primaire
    Le compte principal auquel lutilisateur appartient.
  • Date de suppression prévue
    La date et lheure auxquelles il est prévu que lobjet soit définitivement supprimé. Si la valeur est vide, lobjet ne sera pas supprimé.
  • ID
    A unique identifier for the object.
  • Limite de la demande
    Nombre maximum de requêtes API acceptées toutes les 2 minutes.
  • Nom
    Nom utilisé pour identifier lutilisateur de lapplication.
  • Scope
    Létendue à laquelle lutilisateur appartient.
  • Statut
    Létat actuel de lobjet.

    An application user can have the following states:

    Active

    When the state is set to Active this user can login and execute actions.

    Inactive

    When the state is set to Inactive this user can not login. However, all the information is kept and the user can be activated later.

    Deleting

    The user is in the process of the deletion. This may take some time until the user is marked as Deleting before being marked as Deleted.

    Deleted

    The user is deleted. Since the user is linked with data which cannot be deleted immediately, we need to keep the user until all the data can be removed.

  • User Type
    Le type dutilisateur qui définit son rôle et ses capacités.
  • Version
    The version is used for optimistic locking and incremented whenever the object is updated.