fix: rename ARM_CCA scheme to CCA for consistency

builtin/schemes.gen.go

@@ -5,7 +5,7 @@ import (
 
         scheme1 "github.com/veraison/services/scheme/parsec-cca"
         scheme2 "github.com/veraison/services/scheme/riot"
-        scheme3 "github.com/veraison/services/scheme/arm-cca"
+        scheme3 "github.com/veraison/services/scheme/cca"
         scheme4 "github.com/veraison/services/scheme/tpm-enacttrust"
         scheme5 "github.com/veraison/services/scheme/parsec-tpm"
         scheme6 "github.com/veraison/services/scheme/psa-iot"

deployments/rpm/veraison-services.spec.template

@@ -88,7 +88,7 @@ cp -a $DEPLOYMENT_DEST/* %{buildroot}/
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/evcli
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/pocli
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/veraison
-%attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/arm-cca.plugin
+%attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/cca.plugin
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/parsec-cca.plugin
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/parsec-tpm.plugin
 %attr(0755, %{USERNAME}, %{GROUPNAME}) %{_bindir}/psa.plugin

integration-tests/data/results/cca.freshness-fail.json

@@ -1,6 +1,6 @@
 {
-  "ARM_CCA": {
-    "ear.appraisal-policy-id": "policy:ARM_CCA",
+  "CCA": {
+    "ear.appraisal-policy-id": "policy:CCA",
     "ear.status": "contraindicated",
     "ear.trustworthiness-vector": {
       "configuration": 99,

integration-tests/data/results/cca.good.json

@@ -11,7 +11,7 @@
       "sourced-data": 0,
       "storage-opaque": 2
     },
-    "ear.appraisal-policy-id": "policy:ARM_CCA",
+    "ear.appraisal-policy-id": "policy:CCA",
     "ear.veraison.annotated-evidence": {
       "cca-platform-challenge": "Bea1iETGoM0ZOCBpuv2w5JRmKjrc+P3hFHjpM5Ua8XkP9d5ceOPbESPaCiB6i2ZVbgoi8Z7mS9wviZU7azJVXw==",
       "cca-platform-config": "AQID",
@@ -50,7 +50,7 @@
     }
   },
   "CCA_REALM": {
-    "ear.appraisal-policy-id": "policy:ARM_CCA",
+    "ear.appraisal-policy-id": "policy:CCA",
     "ear.status": "warning",
     "ear.trustworthiness-vector": {
       "configuration": 0,

integration-tests/tests/test_cca_verify_challenge.tavern.yaml

@@ -43,7 +43,7 @@ stages:
   - name: submit cca policy
     request:
       method: POST
-      url: https://{management-service}/management/v1/policy/ARM_CCA
+      url: https://{management-service}/management/v1/policy/CCA
       headers:
         content-type: application/vnd.veraison.policy.opa
         accept: application/vnd.veraison.policy+json
@@ -58,7 +58,7 @@ stages:
   - name: activate cca policy
     request:
       method: POST
-      url: https://{management-service}/management/v1/policy/ARM_CCA/{policy-uuid}/activate
+      url: https://{management-service}/management/v1/policy/CCA/{policy-uuid}/activate
       headers:
         authorization: '{alt-authorization}' # set via hook
     response:

scheme/Makefile

@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: Apache-2.0
 
 SUBDIR := common
-SUBDIR += arm-cca
+SUBDIR += cca
 SUBDIR += riot
 SUBDIR += psa-iot
 SUBDIR += tpm-enacttrust

scheme/README.md

@@ -12,7 +12,7 @@ schemes.
 
 Currently the following schemes are implemented:
 
-- `arm-cca` Arm Confidential Compute Architecture attestation.
+- `cca` Confidential Compute Architecture attestation.
 - `psa-iot`: Arm Platform Security Architecture attestation.
 - `riot`: [RIoT based DICE](https://trustedcomputinggroup.org/work-groups/dice-architectures/)-compatible
   attestation (note: this does not implement any specific DICE architecture).