A Profile represents an external actor that interacts with the system via authenticated API calls. Each profile encapsulates the following core attributes:username: Unique identifier used for authentication
password: Secret credential associated with the username
publicKey: A registered cryptographic public key used for verifying request signatures and securing communication
user: Profile that is using the system for uploading/downloading data, registering devices etc..
device: Storage or Authenticator that is registered under profile
Profile Activation Requirements#
For a profile to become an active and fully functional identity within the system, its associated publicKey must be successfully registered. The absence of a registered key renders the profile incomplete and unable to initiate system-level operations.Note: Public key registration is a mandatory step in the provisioning process. Until this is completed, the profile cannot participate in any authenticated workflow.
Authentication and Token Acquisition#
Before a profile can perform any interaction with protected system resources, it must obtain a valid authorization token. This is achieved through an authentication request using the profile's credentials.
The access_token must be included as a X-DPT-AUTHORIZATION header of all subsequent API requests and as token for all messages that are sent.Summary#
A profile must be provisioned with a username, password, and public key.
Public key registration is required for the profile to become operational.
Upon successful authentication, the system issues a token.
The token must accompany all authorized API requests made by the profile as part of header or in case of messages as part of auth. 