Comment on page

Initialization

Encedo HEM needs to be initialized before it's usable. This process is called Personalization and these two API endpoints are dedicated for this operation.

These two endpoints are wide open and do not need any authorization data. After the successful personalization of the device, future calls will raise Error 406.
The format of the initialization data is described in "General information".
Personalization
Phase 1 - challenge
get
https://my.ence.do
/api/auth/init
Get challenge data
Response data for successful operation
Name
Type
Description
eid
String
EncedoID, public key of the instance
exp
String
Expire timestamp
genuine
String
Attestation data
jti
String
Token id
spk
String
Session public key
Phase 2 - response
post
https://my.ence.do
/api/auth/init
Upload initial configuration
Response data for successful operation
Name
Type
Description
genuine
String
Attestation data
instanceid
String
Instance unique ID
token
String
JWT access token (refered as JWT_TOKEN)
Log entries (directly and indirectly as indicated)
Event
Result
Source
LOG_TYPE_DEVICE_INITED
LOG_RESULT_OK
200
LOG_TYPE_STARTUP
LOG_RESULT_OK
On every powerup as second log entry (the first is LOG_TYPE_KEY_INIT)

Name	Type	Description
`eid`	String	EncedoID, public key of the instance
`exp`	String	Expire timestamp
`genuine`	String	Attestation data
`jti`	String	Token id
`spk`	String	Session public key

Name	Type	Description
`genuine`	String	Attestation data
`instanceid`	String	Instance unique ID
`token`	String	JWT access token (refered as JWT_TOKEN)

Event	Result	Source
LOG_TYPE_DEVICE_INITED	LOG_RESULT_OK	200
LOG_TYPE_STARTUP	LOG_RESULT_OK	On every powerup as second log entry (the first is `LOG_TYPE_KEY_INIT`)

Authorization

User authentication

Last modified 1yr ago