200 for both success and protocol-level failure, so read AO, AN, and BB in the response body rather than relying on the HTTP status code. A response with AO set to ERRO is a failure.
The bridge returns 403
Cause: The endpoint identity is not authorized for the Host API command in theAO field. Creating the AppViewX endpoint authorizes RKPK and RKOP:request automatically, so a 403 usually means the endpoint is missing or disabled, or was created from the wrong template.
Fix: Confirm the AppViewX service is deployed and its endpoint exists and is enabled, as described in Prepare CryptoHub. If the endpoint is absent or was created from a different template, re-create it from the AppViewX service so it carries the RKPK and RKOP:request authorization.
The bridge returns 401
Cause: With the user name and password method, the request carried no valid session. Either the token was omitted, was malformed, or expired. Fix: Confirm theAuthorization header is spelled correctly and carries the current token. Re-authenticate against /home/v1/login and retry. Configure AppViewX to re-authenticate based on tokenExpiration rather than a fixed interval.
The bridge returns 401 Failed to find provider and identity to match client PKI.
Cause: With the client certificate method, CryptoHub could not match the certificate AppViewX presented to a client certificate endpoint identity. The certificate is not from a client certificate endpoint, or CryptoHub did not issue it. A certificate from a user name and password endpoint, or a self-signed certificate with the same subject as the endpoint identity, produces this error.
Fix: Configure AppViewX to present the certificate and key from the pki.p12 in the bundle of a client certificate endpoint of this service. If the AppViewX service was deployed with user name and password authentication, deploy a new AppViewX service with client certificate authentication (TlsBundle) and create an endpoint for it, as described in Prepare CryptoHub.
BB says USER NOT LOGGED IN
Cause: The command reached the device without an authenticated Host API session.
Fix: This indicates the session used for the bridge call is not the session the command sees. Confirm the login succeeded and returned fullyLoggedIn: true, and that the same session is carried on the bridge call.
BB says INVALID KEY USAGE
Cause: The KU value names a usage the key type does not support.
Fix: Send KU as S for asymmetric sign and verify, the usage a CSR-signing key needs. CryptoHub reads the leading usage character, so SV is also accepted as sign and verify. See RKPK: Populate Generated Key Pair for the full list of usage values.
BB says EXPONENT OUT OF RANGE
Cause: The RA value is not a valid RSA exponent. This also occurs when RA is omitted, or when an ECC curve value is sent without setting KT to 2.
Fix: For RSA, send RA as 10001, the hexadecimal form of 65537. The value must be odd. For ECC, set KT to 2 and send the curve in RA: 2 for P-256, 3 for P-384, or 4 for P-521.
BB says UNKNOWN KEY GROUP
Cause: The KG value does not name a key group the AppViewX service role can access. Either the group does not exist, or the role has no access to it.
Fix: Confirm KG matches the key group name exactly. Give the AppViewX service role Add access to the group, as described in Prepare CryptoHub.
BB says KEY GROUP PERMISSIONS LACKING
Cause: The AppViewX service role has access to the key group, but at a level below Add, such as Use or Modify. Generating a key pair into a group requires Add.
Fix: Right-click the key group in Key Management > Key Database, select Permission…, and set the AppViewX service role to Add. See Prepare CryptoHub.
BB says MODULUS SIZE OUT OF RANGE
Cause: The RB value is missing or is not a valid RSA modulus size.
Fix: Send a modulus size divisible by 8, such as 2048 or 4096. For an ECC key pair, set KT to 2 and omit RB.
BB says INVALID MAJOR KEY
Cause: The MK value does not name a recognized major key.
Fix: Send MK as 6 for the PMK, or 1 for the MFK. Confirm the selected major key is loaded on the device.
BB says Invalid hash type.
Cause: The hash selector is outside the supported range. RKOP accepts 1 through 7 only, and 0 is not valid.
Fix: Send 4 for SHA-256, or omit the token to accept the SHA-256 default.
BB says Error generating signature. for an ECC key
Cause: RKOP was sent with RG set to 2 for an ECC key pair. On RKOP, 2 selects MD5, which has no ECDSA form. The response has AO set to ERRO.
Fix: Send RG as 4 for P-256, 5 for P-384, or 6 for P-521. See Choose the signature hash.
The HTTPS connection to CryptoHub fails certificate verification
Cause: AppViewX does not trust the CA that issued the CryptoHub server certificate, or it connects with an address the certificate does not list. Configuringca-chain.pem from the endpoint bundle as the trust anchor also fails, because that file holds the CA certificates for the endpoint’s client certificate, not for the server.
Fix: Trust the CA chain that issued the CryptoHub Dashboard server certificate, and connect with a DNS name in its SAN extension. See Trust the CryptoHub server certificate.
The CSR came back signed with an unexpected hash
Cause: The numeric hash encoding is not uniform across Host API commands. OnRKOP, 2 is MD5, 3 is RIPEMD160, and 4 is SHA-256. A workflow that sends 2 expecting SHA-256 produces an MD5-signed request.
Fix: Send 4 for SHA-256 with an RSA key, or the curve-matched value for an ECC key, then confirm the result with openssl req -inform DER -in request.der -text -noout and check the signatureAlgorithm field. Read the hash table on the reference page for the specific command you send rather than reusing a value from another command.
The key does not appear in the key group
Cause: The generation request sentFC:0, which returns a temporary result that is not stored. An RKPK key pair persists by default, so an explicit FC:0 is the usual cause.
Fix: Omit FC, or send FC:1 to persist explicitly. Confirm the response carries an ID token, which is returned when the key pair is persisted.
The key exists but the symmetric key commands cannot find it
Cause: An RKPK-generated key pair is a PKI key pair, and the symmetric key commands do not operate on it. Fix: Use PGKE: Paginated Keys to list it and RKDP: Delete PKI Key Pair to remove it.BB says ERROR RETRIEVING CERTIFICATE
Cause: The selector in the CSR command does not match an object on the device. In the 7.0.3.x key-name flow, NA does not match a persisted key pair.
Fix: Confirm NA matches the key name recorded when you ran RKPK, and that the key pair persisted. List keys with PGKE: Paginated Keys to verify.
BB says Cannot sign request without private key.
Cause: The object the CSR command selected has no private key to sign with.
Fix: Confirm NA names the RKPK-generated key pair, which holds its private key in the HSM. Confirm the key persisted and appears in PGKE: Paginated Keys.
The issued certificate has no subject alternative names
Cause: CryptoHub does not carry SANs in the CSR, and the certificate authority took SANs only from the CSR extension rather than from the request submission. Fix: Configure the certificate authority to accept SAN values supplied with the request, or configure the certificate template or profile to populate them. Reissue after correcting the configuration.The CSR call returns a selector error
On CryptoHub 7.0.3.x,RKOP with OP=request builds the CSR directly from an RKPK-generated key pair selected by NA, together with the subject-override tokens. The RKOP: Request reference describes the certificate-selector form (CA plus RT, AL, or ID) that later firmware uses.
If the call returns a selector or private key error, confirm you are sending the key-name form for 7.0.3.x: NA set to the RKPK key name, plus the subject tokens. Do not send a CA container selector with NA.

