...
...
| Expand | ||||
|---|---|---|---|---|
| ||||
|
...
Certificates
A digital certificate is used as a proof of identity, and can be compared to a driver’s license or a passport.
| Expand | ||
|---|---|---|
| ||
In the Lequinox® platform, all personal accounts, role accounts, application accesses and server accounts have three certificates used for authentication, encryption and signing. The Lequinox platform uses self-signed X.509 certificates. |
Expired certificates
Every certificate has a set validity period, and once it has expired, it is no longer accepted in the Lequinox platform and needs to be renewed. For example, a sign certificate generally has a validity period of three years.
...
Console administration levels
| Info |
|---|
The administration level applies to internal role accounts and is set when an account is created. |
Organisation user
The lowest console administration level.
| Expand | ||
|---|---|---|
| ||
Accounts with the administration level ‘Organisation user’:
|
Organisation administrator
The highest console administration level for a connected organisation.
| Expand | ||
|---|---|---|
| ||
Accounts with the console administration level ‘Organisation administrator’:
|
Platform administrator
The highest console administration level, reserved for the platform owner. This administration level is not available to connected organisations.
| Expand | ||
|---|---|---|
| ||
Accounts with the console administration level ‘Platform administrator’:
|
...
User accounts
In the platform, a user account can be represented in the form of an internal or external role account, an external personal account (in the REST API referred to as an external personal identity) or a server account. As such, a user account is either of the private, organisation (referred to as corporate in the REST API) or server type. The private and organisation types can be provided with application accesses. The organisation user account types are backed by a personal account (in the REST API referred to as a personal identity), which acts as a witness in transactions.
| Info |
|---|
A server account is platform-managed by design and cannot have a supporting personal identity or any accesses. |
Role accounts
A role account is used as an identifier for a user in an organisation in the Lequinox platform. When created, a role account is assigned a role, and – if it is an internal account – a console administration level.
...
Internal role accounts are primarily intended for users closely linked to your organisation, like employees. External role accounts are intended for users that are not part of your organisation, like contractors, vendors or corporate customers, but with whom you want to interact with via Lequinox-enabled applications to get traceability for these interactions.
| Expand | ||
|---|---|---|
| ||
|
Server accounts
A server account is an account representing the owner of a Lequinox-enabled application, and provides an application with an identity in the platform. A server account can be a creator or a recipient of a transaction, and can be used for automated tasks like opening and signing a transaction, and checking participant status.
...
Roles
When a role account is created, it must be assigned to one of the available roles. Accounts with the console administration levels Organisation and Platform administrator can add and edit internal and external roles associated with the organisation they belong to.
A role is internal or external, depending on whether it is to be assigned to internal role accounts or external role accounts.
| Expand | ||
|---|---|---|
| ||
|
...
Transactions
| Info |
|---|
The term transactions does not refer to financial transactions, but traceable transfers of data with integrity intact. |
The Lequinox platform allows users or applications to create, send and open encrypted transactions via Lequinox-enabled applications. Transactions also include a number of services that affect what a transaction creator or participant can and cannot do, and when.
...