- Application management
- RESTful API
- User API
- Device API
- Get devices
- Get devices extended
- Get device count
- Get device
- Get device by MAC address
- Get device by hostname
- Update device
- Get device threat
- Update device threat
- Get zone devices
- Get agent installer link
- Delete Devices
- Get Device Lifecycle Management settings
- Update Device Lifecycle Management Settings
- Exempt devices from the Device Lifecycle Management process
- Include devices in the Device Lifecycle Management process
- Reset the inactive period for a list of devices that are included in the Device Lifecycle Management process
- Global list API
- Policy API
- Zone API
- Threat API
- Memory protection API
- Detections API
- Package deployment API
- Detection rule API
- Detection rule sets API
- Detection exceptions API
- Device commands API
- Focus view API
- InstaQuery API
- CylanceOPTICS policy API
- Lockdown configurations API
Authentication
During the step which a client system requests access prior to using
BlackBerry
resources, there is an independent web API that will handle the authentication process and grant access to the client system. A token based authentication approach is being taken as a means of data transportation between the parties. BlackBerry
has adopted JWT (RFC 7519) as the token format for its simplicity as well as its capabilities for digital signature.The following actors exist in the authentication workflow:
- Authentication Token: Created and signed by the client system to perform an authentication request, it is in this request where the application is indicated.
- Authentication Endpoint: Part of theBlackBerryAuth web API which will handle the authentication requests coming from client systems, there will be a particular endpoint to handle JWT tokens.
- Access Token: If authentication is successful and the client system is granted access to the requested application, a token representing this identity and some key attributes will be returned as a JWT token.