- Overview
- CylanceON-PREM architecture
- Steps to get Start with CylanceON-PREM
- Requirements: CylanceON-PREM
- Configuring the CylanceON-PREM virtual appliance
- Configuring the console
- Log in to CylanceON-PREM
- Administrative dashboard
- Filter lists
- Export lists
- Policies
- Setting up the CylancePROTECT agent
- Adding the CA certificate to endpoints
- Installing the CylancePROTECT Desktop agent for Windows
- Installing the CylancePROTECT Desktop agent for macOS
- Installing the CylancePROTECT Desktop agent for Linux
- Manually update the Linux driver
- Upgrading the CylancePROTECT Desktop agents
- Using virtual machines
- Device management
- Threat management
- Global lists
- Administration
- Managing users
- Managing roles
- Update profile information
- Audit logs
- Managing Certificates
- Setting up email notifications
- Settings
- Upgrade CylanceON-PREM
- Reboot the virtual appliance
- Configure session timeout
- Update CylanceON-PREM SSL certificate version 1.3.1 and later
- Update CylanceON-PREM SSL certificate version 1.2.2.1 and earlier
- Change the certificate cipher mode
- Enable maintenance mode
- Change network settings
- Check an IP address
- Change the log level
- Download logs
- Configure syslog/SIEM settings
- Update database connection settings
- Configure active directory
- Configure identity provider settings
- Using certificate-based authentication
- Add a banner to the login screen
- Applications
- CylanceON-PREM API
- Troubleshooting
- Agent not communicating with CylanceON-PREM
- Web browser reports insecure webpage
- Unable to connect to external database
- Configure static IP using the OVF tool
- Remote server 404 error in log files
- Log in with a local administrator account
- Online Certificate Status Protocol issues
- A user is not receiving email notifications
- Before you contact support
- BlackBerry Docs
- CylanceON-PREM
- Cylance ONPREM Administration Guide
- CylanceON-PREM API
- Application management
- Apply missing header information
Apply missing header information
The YAML file does not include the access token required to make an API request. You will need to include additional header information in the request.
Curl requests
For example, for the GET Devices call, if you use the YAML File in Swagger with the default options selected and https://login.onprem-cylance.com/cyapi/v1/client is set as the server, the following Curl command is generated:
curl -X GET "https://login.onprem-cylance.com/cyapi/v1/client/devices?page=1&pageSize=50&includeMeta=true" -H "accept: application/json"
However, for this command to work, you must include the access token:
curl -X GET "https://login.onprem-cylance.com/cyapi/v1/client/devices?page=1&pageSize=50&includeMeta=true" -H "accept: application/json" -H "authorization: Bearer {{access-token}}"
curl -X GET "https://login.onpremcylance.com/cyapi/v1/client/devices?page=1&pageSize=50&includeMeta=true" -H "accept: application/json" -H "authorization: Bearer {{accesstoken}}"
Replace {{access-token}} with the access token you generated using your application ID and application secret. See Access token .
Request URL
For example, for the GET Devices call, if you use the YAML file in Swagger with the default options selected and https://login.onprem-cylance.com/cyapi/v1/client is set as the server, the following URL command is generated:
https://login.onprem-cylance.com/cyapi/v1/client/devices?page=1&pageSize=100
However, for the command to work, it will require the following Headers:
- Accept: application/json
- Authorization: Bearer {{access-token}}
Replace {{access-token}} with the access token you generated using your application ID and application secret. See Access token .