About Qeo Platform Security
The Qeo Platform API allows one to handle the Device Registration procedure in a platform specific way.
It offers full flexibility to the Platform Integrator for choosing:
- The Local Registration procedure or the Remote Registration procedure.
- The way to interact with the user during the registration procedure, i.e., getting input from the user or providing progress information to the user.
The API
The Qeo Platform Security C API (platform_api.h) allows for registering the following call-back functions:
- qeo_platform_on_registration_params_needed_cb:
Called whenever Qeo needs registration data:- One Time Code (OTC) and URL of the Security Management Server (SMS) in case of the Local Registration procedure.
- Suggested user name and registration window value in case of the Remote Registration procedure.
- qeo_platform_on_security_status_update_cb:
Called by Qeo to provide progress information about the registration procedure.
- qeo_platform_on_remote_registration_confirmation_needed_cb:
Called when Qeo needs confirmation to use the registration credentials obtained at a certain stage during the Remote Registration procedure.
For each call-back that is not registered, the default implementation is used. Go here for more info: Setting Up Remote Registration.
The API also provides functions to:
- Pass on the OTC and URL of the SMS in case of the Local Registration procedure.
- Pass on the suggested user name and registration window value in case of the Remote Registration procedure.
- Confirm proceeding with the Remote Registration procedure.
- Cancel the registration procedure.