- Added 11/2026 - Added ECC key generation (NIST P-256, P-384, and P-521) with the matching
RKOPsignature hash for each curve, and a warning thatRGset to2fails for ECC keys. - Updated 11/2026 - Prepare CryptoHub now gives the AppViewX service role Add access to the key group, which key generation requires. Removed the note that the key group’s settings constrain the generated keys: a key pair keeps the algorithm and size in its request, so one group can hold both RSA and ECC keys.
- Updated 11/2026 - Added the server certificate AppViewX must trust: the CA chain of the CryptoHub Dashboard certificate, reached by a DNS name in its SAN extension, not
ca-chain.pemfrom the endpoint bundle. Corrected the login and key generation response examples, and replaced the workflow image with a diagram that covers both authentication methods and both key algorithms.
- Updated 11/2026 - Added client certificate authentication as an alternative to user name and password. When you deploy the AppViewX service, choose the endpoint authentication under Service Info > Authentication Mechanisms:
UserPass(the default) orTlsBundle. WithTlsBundle, AppViewX presents the client certificate from the endpoint bundle on every request to the Excrypt protocol bridge, with no login call or token. Removed the fixed token lifetime from the user name and password method; AppViewX honorstokenExpirationinstead.
- Updated 08/2026 - Set the service endpoint to the CryptoHub REST API port (
apiType: RestApi), so the endpoint identity authenticates over the REST API with no manual configuration. Enabling REST API Login on the endpoint’s partition is no longer required, and the integration no longer uses the JSON Excrypt Port: all operations run over the REST API and the REST Excrypt protocol bridge (/home/v1/excrypt).
- Updated 08/2026 - Re-scoped CryptoHub preparation to the service-template deploy and endpoint model. Deploying the AppViewX service and creating an endpoint now provisions the scoped partition and identity, provisions its access, and authorizes the Host API commands (
RKPK,RKOP:request) automatically. Creating the key group remains manual.

