Managing App Signing Certificates
4 items
Managing Key Sets
When an Approov account is created it is allocated a random secret key that is used by default for Approov token signing or encryption. This provides Approov tokens signed using the HS256 algorithm (or A256GCMKW if an encrypted JWE is selected). The HS256 verification uses the symmetric 512-bit account secret key, which needs to be made available to the backend API, to check the validity of the token.
Message Signing
2 items
User Management
It is possible to provide access to your Approov account (via the approov CLI) to other members of your team.
Service Monitoring
Approov provides facilities that allows monitoring of the status of your account. A healthcheck API endpoint is supported, along with monthly or even daily summaries of usage. There is also the option for notification emails if there is a certificate or API access problem with one of your endpoints, or if there are elevated attestation failures in your account.
Metrics Graphs
3 items
Automated Approov CLI
You may wish to use the Approov CLI from within automated scripts, perhaps on remote runner machines for Continuous Integration (CI) systems. In this case the interative approov role mechanism may not be appropriate, since it requires a user to type in the password and the session only lasts for one hour. Thus a mechanism is provided whereby an automation role management token can be defined in a local environment variable to provide Approov account access. This will not be password protected.