Error Handling in Fortanix Confidential Computing Manager

  • Published on Jun 11, 2024
  • 1 minute(s) read

Error Handling During Application Creation

  • 403 - Quota Exceeded error: The current limit for application creation in Fortanix Confidential Computing Manager (CCM) is ten (10) applications per account. So, if the user tries to create the 11th application, the following 403 error will be displayed.  

    CCM_73.png

    Figure 1: 403 App Quota Eerror

  • 400 – Application already present in the system error: When the user tries to create an application with the same name as an existing application that was previously created, then the following error will be displayed.  

    400 ERROR APP ALREADY PRESENT.png

    Figure 2: 400 Error App Already Present

  • 500 – Internal server error: This error appears when something went wrong with the Fortanix CCM server, but the server could not be more specific on what the exact problem is. Retry again.

Error Handling for Application Update

  • 400 – Pending domain whitelist tasks: When the user is trying to update the domain of a certificate, but the previous domain was still not approved/declined then the following error will be displayed.  

    400 ERROR PENDING DOMAIN WHITELIST TASKS.png

    Figure 3: 400 Error Pending Domain Whitelist Tasks

  • 500 – Internal server error: This error appears when something went wrong with the Fortanix CCM server, but the server could not be more specific on what the exact problem is. Retry again.

Error Handling for Image Creation

  • 403 – Quota Exceeded: The current limit for build creation in Fortanix CCM is ten (10) images per application. So, if the user tries to create the 11th image, the following 403 error will be displayed.  

    CCM_76.png

    Figure 4: 403 Image Quota Exceeded

  • 400 – Bad request error: While creating an image for an EDP application If the user tries to use the same Enclave Sigstruct values then the following error will be displayed since MRENCLAVE is unique and cannot be the same for any two builds in an account.  

    400 BAD REQUEST ERROR.png

    Figure 5: 400 Bad Request Error

  • 500 – Internal server error: This error appears when something went wrong with the Fortanix CCM server, but the server could not be more specific on what the exact problem is. Retry again.

Error Handling for Compute Node Enrollment

During the compute node enrollment process, when the IAS Attestation fails for the compute node then the compute node will appear as “Unprovisioned” in the Compute Nodes.

For more details about the IAS attestation process, refer to the article: Fortanix Confidential Computing Manager SGX Attestation Process.

unprovisioned.png

Figure 6: IAS Attestation Failure for Compute Node Enrollment

Related articles