"use strict";
var import_Resource = require("#models/Resource.js");
/**
 * @license
 * Copyright 2022-2026 Matter.js Authors
 * SPDX-License-Identifier: Apache-2.0
 */
import_Resource.Resource.add({
  tag: "cluster",
  name: "OperationalCredentials",
  pics: "OPCREDS",
  xref: "core\xA711.18",
  details: "This cluster is used to add or remove Node Operational credentials on a Commissionee or already-configured Node, as well as manage the associated Fabrics.",
  children: [
    {
      tag: "attribute",
      name: "Nocs",
      xref: "core\xA711.18.5.1",
      details: "This attribute shall contain all NOCs applicable to this Node, encoded as a read-only list of NOCStruct.\nOperational Certificates shall be added through the AddNOC command, and shall be removed through the RemoveFabric command.\nUpon Factory Data Reset, this attribute shall be set to a default value of an empty list.\nThe number of entries in this list shall match the number of entries in the Fabrics attribute."
    },
    {
      tag: "attribute",
      name: "Fabrics",
      xref: "core\xA711.18.5.2",
      details: 'Indicates all fabrics to which this Node is commissioned, encoded as a read-only list of FabricDescriptorStruct. This information may be computed directly from the NOCs attribute.\nThe Fabrics attribute is also known as "the fabric table".\nUpon Factory Data Reset, this attribute shall be set to a default value of an empty list.\nThe number of entries in this list shall match the number of entries in the NOCs attribute.'
    },
    {
      tag: "attribute",
      name: "SupportedFabrics",
      xref: "core\xA711.18.5.3",
      details: "Indicates the number of Fabrics that are supported by the device. This value is fixed for a particular device."
    },
    {
      tag: "attribute",
      name: "CommissionedFabrics",
      xref: "core\xA711.18.5.4",
      details: "Indicates the number of Fabrics to which the device is currently commissioned. This attribute shall be equal to the following:\n  - The number of entries in the NOCs attribute.\n  - The number of entries in the Fabrics attribute.\nUpon Factory Data Reset, this attribute shall be set to a default value of 0."
    },
    {
      tag: "attribute",
      name: "TrustedRootCertificates",
      xref: "core\xA711.18.5.5",
      details: "This attribute shall contain the list of Trusted Root CA Certificates (RCAC) installed on the Node, as octet strings containing their Matter Certificate Encoding representation.\nThese certificates are installed through the AddTrustedRootCertificate command.\nDepending on the method of storage employed by the server, either shared storage for identical root certificates shared by many fabrics, or individually stored root certificate per fabric, multiple identical root certificates may legally appear within the list.\nTo match a root with a given fabric, the root certificate\u2019s subject and subject public key need to be cross-referenced with the NOC or ICAC certificates that appear in the NOCs attribute for a given fabric.\nUpon Factory Data Reset, this attribute shall be set to a default value whereby the list is empty."
    },
    {
      tag: "attribute",
      name: "CurrentFabricIndex",
      xref: "core\xA711.18.5.6",
      details: "Indicates the accessing fabric index.\nThis attribute is useful to contextualize Fabric-Scoped entries obtained from response commands or attribute reads, since a given Fabric may be referenced by a different Fabric Index locally on a remote Node."
    },
    {
      tag: "command",
      name: "AttestationRequest",
      xref: "core\xA711.18.6.1",
      details: "This command is used to perform an attestation request.\nThis command shall be generated to request the Attestation Information, in the form of an AttestationResponse Command. If the AttestationNonce that is provided in the command is malformed, a recipient shall fail the command with a Status Code of INVALID_COMMAND. The AttestationNonce field shall be used in the computation of the Attestation Information."
    },
    {
      tag: "command",
      name: "AttestationResponse",
      xref: "core\xA711.18.6.2",
      details: "This command is used to report the results of the AttestationRequest command. This command shall be generated in response to an Attestation Request command.\nSee Section 11.18.4.7, \u201CAttestation Information\u201D for details about the generation of the fields within this response command.\nSee Section F.2, \u201CDevice Attestation Response test vector\u201D for an example computation of an AttestationResponse.",
      children: [
        {
          tag: "field",
          name: "AttestationElements",
          xref: "core\xA711.18.6.2.1",
          details: "This field shall contain the octet string of the serialized attestation_elements_message."
        },
        {
          tag: "field",
          name: "AttestationSignature",
          xref: "core\xA711.18.6.2.2",
          details: "This field shall contain the octet string of the necessary attestation_signature as described in Section 11.18.4.7, \u201CAttestation Information\u201D."
        }
      ]
    },
    {
      tag: "command",
      name: "CertificateChainRequest",
      xref: "core\xA711.18.6.3",
      details: "This command is used to request a certificate from the device attestation certificate chain.\nIf the CertificateType is not a valid value per CertificateChainTypeEnum then the command shall fail with a Status Code of INVALID_COMMAND."
    },
    {
      tag: "command",
      name: "CertificateChainResponse",
      xref: "core\xA711.18.6.4",
      details: "This command is used to report the results of the CertificateChainRequest command. This command shall be generated in response to a CertificateChainRequest command.",
      children: [{
        tag: "field",
        name: "Certificate",
        xref: "core\xA711.18.6.4.1",
        details: "This field shall be the DER encoded certificate corresponding to the CertificateType field in the CertificateChainRequest command."
      }]
    },
    {
      tag: "command",
      name: "CsrRequest",
      xref: "core\xA711.18.6.5",
      details: "This command is used to perform a CSR request.\nThis command shall be generated to execute the Node Operational CSR Procedure and subsequently return the NOCSR Information, in the form of a CSRResponse Command.\nThe CSRNonce field shall be used in the computation of the NOCSR Information. If the CSRNonce is malformed, then this command shall fail with an INVALID_COMMAND status code.\nIf the IsForUpdateNOC field is present and set to true, but the command was received over a PASE session, the command shall fail with an INVALID_COMMAND status code, as it would never be possible to use a resulting subsequent certificate issued from the CSR with the UpdateNOC command, which is forbidden over PASE sessions.\nIf the IsForUpdateNOC field is present and set to true, the internal state of the CSR associated key pair shall be tagged as being for a subsequent UpdateNOC, otherwise the internal state of the CSR shall be tagged as being for a subsequent AddNOC. See Section 11.18.6.8, \u201CAddNOC Command\u201D and Section 11.18.6.9, \u201CUpdateNOC Command\u201D for details about the processing.\nIf this command is received without an armed fail-safe context (see Section 11.10.7.2, \u201CArmFailSafe Command\u201D), then this command shall fail with a FAILSAFE_REQUIRED status code sent back to the initiator.\nIf a prior UpdateNOC or AddNOC command was successfully executed within the fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf the Node Operational Key Pair generated during processing of the Node Operational CSR Procedure is found to collide with an existing key pair already previously generated and installed, and that check had been executed, then this command shall fail with a FAILURE status code sent back to the initiator."
    },
    {
      tag: "command",
      name: "CsrResponse",
      xref: "core\xA711.18.6.6",
      details: "This command is used to report the results of the CSRRequest command. This command shall be generated in response to a CSRRequest Command.\nSee Section 11.18.4.9, \u201CNOCSR Information\u201D for details about the generation of the fields within this response command.\nSee Section F.3, \u201CNode Operational CSR Response test vector\u201D for an example computation of a CSRResponse.",
      children: [
        {
          tag: "field",
          name: "NocsrElements",
          xref: "core\xA711.18.6.6.1",
          details: "This field shall contain the octet string of the serialized nocsr_elements_message."
        },
        {
          tag: "field",
          name: "AttestationSignature",
          xref: "core\xA711.18.6.6.2",
          details: "This field shall contain the octet string of the necessary attestation_signature as described in Section 11.18.4.9, \u201CNOCSR Information\u201D."
        }
      ]
    },
    {
      tag: "command",
      name: "AddNoc",
      xref: "core\xA711.18.6.8",
      details: "This command is used to add a new NOC to the device.\nThis command shall add a new NOC chain to the device and commission a new Fabric association upon successful validation of all arguments and preconditions.\nThe new value shall immediately be reflected in the NOCs list attribute.\nA Commissioner or Administrator shall issue this command after issuing the CSRRequest command and receiving its response.\nA Commissioner or Administrator SHOULD issue this command after performing the Attestation Procedure.",
      children: [
        {
          tag: "field",
          name: "IpkValue",
          xref: "core\xA711.18.6.8.1",
          details: "This field shall contain the value of the Epoch Key for the Identity Protection Key (IPK) to set for the Fabric which is to be added. This is needed to bootstrap a necessary configuration value for subsequent CASE to succeed. See Section 4.14.2.6.1, \u201CIdentity Protection Key (IPK)\u201D for details.\nThe IPK shall be provided as an octet string of length CRYPTO_SYMMETRIC_KEY_LENGTH_BYTES.\nOn successful execution of the AddNOC command, the side-effect of having provided this field shall be equivalent to having done a GroupKeyManagement cluster KeySetWrite command invocation using the newly joined fabric as the accessing fabric and with the following argument fields (assuming KeySetWrite allowed a GroupKeySetID set to 0):"
        },
        {
          tag: "field",
          name: "CaseAdminSubject",
          xref: "core\xA711.18.6.8.2",
          details: 'If the AddNOC command succeeds according to the semantics of the following subsections, then the Access Control subject-id shall be used to atomically add an Access Control Entry enabling that Subject to subsequently administer the Node whose operational identity is being added by this command.\nThe format of the new Access Control Entry, created from this, shall be:\n> [!NOTE]\n> Unless such an Access Control Entry is added atomically as described here, there would be no way for the caller on its given Fabric to eventually add another Access Control Entry for CASE authentication mode, to enable the new Administrator to administer the device, since the Fabric Scoping of the Access Control List prevents the current Node from being able to write new entries scoped to that Fabric, if the session is established from CASE. While a session established from PASE does gain Fabric Scope of a newly-joined Fabric, this argument is made mandatory to provide symmetry between both types of session establishment, both of which need to eventually add an "Administer Node over CASE" Access Control Entry to finalize new Fabric configuration and subsequently be able to call the CommissioningComplete command.'
        },
        {
          tag: "field",
          name: "AdminVendorId",
          xref: "core\xA711.18.6.8.3",
          details: 'This field shall be set to the Vendor ID of the entity issuing the AddNOC command. This value shall NOT be one of the reserved Vendor ID values defined in Table 1, \u201CVendor ID Allocations\u201D.\n### Effect on Receipt\nIf this command is received without an armed fail-safe context (see Section 11.10.7.2, \u201CArmFailSafe Command\u201D), then this command shall fail with a FAILSAFE_REQUIRED status code sent back to the initiator.\nIf a prior UpdateNOC or AddNOC command was successfully executed within the fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf the prior CSRRequest state that preceded AddNOC had the IsForUpdateNOC field indicated as true, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf no prior AddTrustedRootCertificate command was successfully executed within the fail-safe timer period, then this command shall process an error by responding with a NOCResponse with a StatusCode of InvalidNOC as described in Section 11.18.6.7.2, \u201CHandling Errors\u201D. In other words, AddNOC always requires that the client provides the root of trust certificate within the same Fail-Safe context as the rest of the new fabric\u2019s operational credentials, even if some other fabric already uses the exact same root of trust certificate.\nIf the NOC provided in the NOCValue encodes an Operational Identifier for a <Root Public Key, FabricID> pair already present on the device, then the device shall process the error by responding with a StatusCode of FabricConflict as described in Section 11.18.6.7.2, \u201CHandling Errors\u201D.\nIf the device already has the CommissionedFabrics attribute equal to the SupportedFabrics attribute, then the device\u2019s operational credentials table is considered full and the device shall process the error by responding with a StatusCode of TableFull as described in Section 11.18.6.7.2, \u201CHandling Errors\u201D.\nIf the CaseAdminSubject field is not a valid ACL subject in the context of AuthMode set to CASE, such as not being in either the Operational or CASE Authenticated Tag range, then the device shall process the error by responding with a StatusCode of InvalidAdminSubject as described in Section 11.18.6.7.2, \u201CHandling Errors\u201D.\nOtherwise, the command is considered an addition of credentials, also known as "joining a fabric", and the following shall apply:\n  1. A new FabricIndex shall be allocated, taking the next valid fabric-index value in monotonically incrementing order, wrapping around from 254 (0xFE) to 1, since value 0 is reserved and using 255 (0xFF) would prevent cluster specifications from using nullable fabric-idx fields.\n  2. An entry within the Fabrics attribute table shall be added, reflecting the matter-fabric-id RDN within the NOC\u2019s subject, along with the public key of the trusted root of the chain and the AdminVendorID field.\n  3. The operational key pair associated with the incoming NOC from the NOCValue, and generated by the prior CSRRequest command, shall be recorded for subsequent use during CASE within the fail-safe timer period (see Section 5.5, \u201CCommissioning Flows\u201D).\n  4. The incoming NOCValue and ICACValue (if present) shall be stored under the FabricIndex associated with the new Fabric Scope, along with the RootCACertificate provided with the prior successful AddTrustedRootCertificate command invoked in the same fail-safe period.\n    a. Implementation of certificate chain storage may separate or otherwise encode the components of the array in implementation-specific ways, as long as they follow the correct format when being read from the NOCs list or used within other protocols such as CASE.\n  5. The NOCs list shall reflect the incoming NOC from the NOCValue field and ICAC from the ICACValue field (if present).\n  6. The operational discovery service record shall immediately reflect the new Operational Identifier, such that the Node immediately begins to exist within the Fabric and becomes reachable over CASE under the new operational identity.\n  7. The receiver shall create and add a new Access Control Entry using the CaseAdminSubject field to grant subsequent Administer access to an Administrator member of the new Fabric. It is recommended that the Administrator presented in CaseAdminSubject exist within the same entity that is currently invoking the AddNOC command, within another of the Fabrics of which it is a member.\n    a. If the Managed Device Feature is implemented by the ACL cluster, then one or more ARL entries with the new FabricIndex may be added to the ARL attribute.\n  8. The incoming IPKValue shall be stored in the Fabric-scoped slot within the Group Key Management cluster (see Section 11.2.7.1, \u201CKeySetWrite Command\u201D), for subsequent use during CASE.\n  9. The Fabric Index associated with the armed fail-safe context (see Section 11.10.7.2, \u201CArmFailSafe Command\u201D) shall be updated to match the Fabric Index just allocated.\n  10. If the current secure session was established with PASE, the receiver shall:\n    a. Augment the secure session context with the FabricIndex generated above, such that subsequent interactions have the proper accessing fabric.\n  11. If the current secure session was established with CASE, subsequent configuration of the newly installed Fabric requires the opening of a new CASE session from the Administrator from the Fabric just installed. This Administrator is the one listed in the CaseAdminSubject argument.\nThereafter, the Node shall respond with an NOCResponse with a StatusCode of OK and a FabricIndex field matching the FabricIndex under which the new Node Operational Certificate (NOC) is scoped.'
        }
      ]
    },
    {
      tag: "command",
      name: "UpdateNoc",
      xref: "core\xA711.18.6.9",
      details: "This command is used to update an existing NOC on the device.\nThis command shall replace the NOC and optional associated ICAC (if present) scoped under the accessing fabric upon successful validation of all arguments and preconditions. The new value shall immediately be reflected in the NOCs list attribute.\nA Commissioner or Administrator shall issue this command after issuing the CSRRequest Command and receiving its response.\nA Commissioner or Administrator SHOULD issue this command after performing the Attestation Procedure.\n### Effect on Receipt\nIf this command is received without an armed fail-safe context (see Section 11.10.7.2, \u201CArmFailSafe Command\u201D), then this command shall fail with a FAILSAFE_REQUIRED status code sent back to the initiator.\nIf a prior UpdateNOC or AddNOC command was successfully executed within the fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf a prior AddTrustedRootCertificate command was successfully invoked within the fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator, since the only valid following logical operation is invoking the AddNOC command.\nIf the prior CSRRequest state that preceded UpdateNOC had the IsForUpdateNOC field indicated as false, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf any of the following conditions arise, the Node shall process an error by responding with an NOCResponse with a StatusCode of InvalidNOC as described in Section 11.18.6.7.2, \u201CHandling Errors\u201D:\n  - The NOC provided in the NOCValue does not refer in its subject to the FabricID associated with the accessing fabric.\n  - The ICAC provided in the ICACValue (if present) has a FabricID in its subject that does not match the FabricID associated with the accessing fabric.\nOtherwise, the command is considered an update of existing credentials for a given Fabric, and the following shall apply:\n  1. The Operational Certificate under the accessing fabric index in the NOCs list shall be updated to match the incoming NOCValue and ICACValue (if present), such that the Node\u2019s Operational Identifier within the Fabric immediately changes.\n    a. The operational key pair associated with the incoming NOC from the NOCValue, and generated by the prior CSRRequest command, shall be committed to permanent storage, for subsequent use during CASE.\n    b. The operational discovery service record shall immediately reflect the new Operational Identifier.\n    c. All internal data reflecting the prior operational identifier of the Node within the Fabric shall be revoked and removed, to an outcome equivalent to the disappearance of the prior Node, except for the ongoing CASE session context, which shall temporarily remain valid until the NOCResponse has been successfully delivered or until the next transport-layer error, so that the response can be received by the Administrator invoking the command.\nThereafter, the Node shall respond with an NOCResponse with a StatusCode of OK and a FabricIndex field matching the FabricIndex under which the updated NOC is scoped."
    },
    {
      tag: "command",
      name: "NocResponse",
      xref: "core\xA711.18.6.10",
      details: "This command is used to report the results of the AddNOC, UpdateNOC, UpdateFabricLabel and RemoveFabric commands.\nThis command shall be generated in response to the following commands:\n  - AddNOC\n  - UpdateNOC\n  - UpdateFabricLabel\n  - RemoveFabric\nIt provides status information about the success or failure of those commands.",
      children: [
        {
          tag: "field",
          name: "StatusCode",
          xref: "core\xA711.18.6.10.1",
          details: "This field shall contain an NOCStatus value representing the status of an operation involving a NOC."
        },
        {
          tag: "field",
          name: "FabricIndex",
          xref: "core\xA711.18.6.10.2",
          details: "If present, it shall contain the Fabric Index of the Fabric last added, removed or updated."
        },
        {
          tag: "field",
          name: "DebugText",
          xref: "core\xA711.18.6.10.3",
          details: "This field may contain debugging textual information from the cluster implementation, which SHOULD NOT be presented to user interfaces in any way. Its purpose is to help developers in troubleshooting errors and the contents may go into logs or crash reports."
        }
      ]
    },
    {
      tag: "command",
      name: "UpdateFabricLabel",
      xref: "core\xA711.18.6.11",
      details: "This command is used to set the user-visible fabric label for a given Fabric.\nThis command shall be used by an Administrator to set the user-visible Label field for a given Fabric, as reflected by entries in the Fabrics attribute. An Administrator shall use this command to set the Label to a string (possibly selected by the user themselves) that the user can recognize and relate to this Administrator\n  - during the commissioning process, and\n  - whenever the user chooses to update this string.\nThe Label field, along with the VendorID field in the same entry of the Fabrics attribute, SHOULD be used by Administrators to provide additional per-fabric context when operations such as RemoveFabric are considered or used.",
      children: [{
        tag: "field",
        name: "Label",
        xref: "core\xA711.18.6.11.1",
        details: "This field shall contain the label to set for the fabric associated with the current secure session.\n### Effect on Receipt\nIf the Label field is identical to a Label already in use by a Fabric within the Fabrics list that is not the accessing fabric, then an NOCResponse with a StatusCode of LabelConflict shall be returned for the command and there shall NOT be any permanent changes to any Fabric data.\nOtherwise, the Label field for the accessing fabric shall immediately be updated to reflect the Label argument provided. Following the update, an NOCResponse with a StatusCode of OK shall be returned.\nIf the command was invoked within a fail-safe context after a successful UpdateNOC command, then the label update shall apply to the pending update state that will be reverted if fail-safe expires prior to a CommissioningComplete command. In other words, label updates apply to the state of the Fabrics Attribute as currently visible, even for an existing fabric currently in process of being updated."
      }]
    },
    {
      tag: "command",
      name: "RemoveFabric",
      xref: "core\xA711.18.6.12",
      details: "This command is used to remove a Fabric from the device.\nThis command is used by Administrators to remove a given Fabric and delete all associated fabric-scoped data.\nIf the given Fabric being removed is the last one to reference a given Trusted Root CA Certificate stored in the Trusted Root Certificates list, then that Trusted Root Certificate shall be removed.\n> [!WARNING]\n> This command, if referring to an already existing Fabric not under the control of the invoking Administrator, shall ONLY be invoked after obtaining some form of explicit user consent through some method executed by the Administrator or Commissioner. This method of obtaining consent SHOULD employ as much data as possible about the existing Fabric associations within the Fabrics list, so that likelihood is as small as possible of a user removing a Fabric unwittingly. If a method exists for an Administrator or Commissioner to convey Fabric Removal to an entity related to that Fabric, whether in-band or out-of-band, then this method SHOULD be used to notify the other Administrative Domain\u2019s party of the removal. Otherwise, users may only observe the removal of a Fabric association as persistently failing attempts to reach a Node operationally.",
      children: [{
        tag: "field",
        name: "FabricIndex",
        xref: "core\xA711.18.6.12.1",
        details: "This field shall contain the Fabric Index reference (see Section 7.19.2.23, \u201CFabric Index Type\u201D) associated with the Fabric which is to be removed from the device.\n### Effect on Receipt\nIf the FabricIndex field does not match the FabricIndex of any entry within the Fabrics list, then an NOCResponse with a StatusCode of InvalidFabricIndex shall be returned for the command and there shall NOT be any permanent changes to any device data.\nOtherwise, one of the following outcomes shall occur:\n  1. If the FabricIndex matches the last remaining entry in the Fabrics list, then the device shall delete all Matter related data on the node which was created since it was commissioned. This includes all Fabric-Scoped data, including Access Control List, Access Restriction List, bindings, scenes, group keys, operational certificates, etc. All Trusted Roots shall also be      removed. If a time synchronization cluster is present on the Node, the TrustedTimeSource and DefaultNtp shall be set to null. Any Matter related data including logs, secure sessions, exchanges and interaction model constructs shall also be removed. Since this operation involves the removal of the secure session data that may underpin the current set of exchanges, the Node invoking the command SHOULD NOT expect a response before terminating its secure session with the target.\n  2. If the FabricIndex does not equal the accessing fabric index, then the device shall begin the process of irrevocably deleting all associated Fabric-Scoped data, including Access Control Entries, Access Restriction Entries, bindings, group keys, operational certificates, etc. Any remaining Trusted Roots no longer referenced by any operational certificate shall also be      removed. If a time synchronization cluster is present on the Node, and the TrustedTimeSource FabricIndex matches the given FabricIndex, the TrustedTimeSource shall be set to null. All secure sessions, exchanges and interaction model constructs related to the Operational Identity under the given Fabric shall also be removed. Following the removal, an NOCResponse with a StatusCode of OK shall be returned.\n  3. If the FabricIndex equals the accessing fabric index, then the device shall begin the process of irrevocably deleting all associated Fabric-Scoped data, including Access Control Entries, Access Restriction Entries, bindings, group keys, operational certificates, etc. Any remaining Trusted Roots no longer referenced by any operational certificate shall also be removed. If a time synchronization cluster is present on the Node, and the TrustedTimeSource FabricIndex matches the given FabricIndex, the TrustedTimeSource shall be set to null. All secure sessions, exchanges and interaction model constructs related to the Operational Identity under the given Fabric shall also be removed. Since this operation involves the removal of the secure session data that may underpin the current set of exchanges, the Node invoking the command SHOULD NOT expect a response before terminating its secure session with the target."
      }]
    },
    {
      tag: "command",
      name: "AddTrustedRootCertificate",
      xref: "core\xA711.18.6.13",
      details: "This command is used to add a trusted root certificate to the device.\nThis command shall add a Trusted Root CA Certificate, provided as its Matter Certificate Encoding representation, to the TrustedRootCertificates Attribute list and shall ensure the next AddNOC command executed uses the provided certificate as its root of trust.\nIf the certificate from the RootCACertificate field is already installed, based on exact byte-for-byte equality, then this command shall succeed with no change to the list.\nIf this command is received without an armed fail-safe context (see Section 11.10.7.2, \u201CArmFailSafe Command\u201D), then this command shall fail with a FAILSAFE_REQUIRED status code sent back to the initiator.\nIf a prior AddTrustedRootCertificate command was successfully invoked within the fail-safe timer period, which would cause the new invocation to add a second root certificate within a given fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf a prior UpdateNOC or AddNOC command was successfully executed within the fail-safe timer period, then this command shall fail with a CONSTRAINT_ERROR status code sent back to the initiator.\nIf the certificate from the RootCACertificate field fails any validity checks, not fulfilling all the requirements for a valid Matter Certificate Encoding representation, including a truncated or oversize value, then this command shall fail with an INVALID_COMMAND status code sent back to the initiator.\nNote that the only method of removing a trusted root is by removing the Fabric that uses it as its root of trust using the RemoveFabric command."
    },
    {
      tag: "command",
      name: "SetVidVerificationStatement",
      xref: "core\xA711.18.6.14",
      details: "This command is used to manage the VendorID and VIDVerificationStatement fields of the Fabrics attribute, and the VVSC field of an entry in the NOCs attribute.\nThis command shall be used to one or more of the following:\n  - Update the VendorID associated with an entry in the Fabrics attribute.\n  - Associate or remove a VIDVerificationStatement associated with an entry in the Fabrics attribute.\n  - Associate or remove a VendorVerificationSigningCertificate (VVSC) associated with an entry in the NOCs attribute.\nThis command shall only operate against the Fabrics and NOCs attribute entries associated with the accessing fabric index.\n### Effect on Receipt\nIf the VendorID field is present, the value of the VendorID in the Fabrics attribute entry associated with the accessing fabric index shall have its value replaced with the value from the command field.\nIf the VVSC field is present, but the ICAC field is already present in the NOCs attribute entry associated with the accessing fabric index, then the command shall fail with a status code of INVALID_COMMAND.\nIf the VIDVerificationStatement field is present:\n  - If the length of the field\u2019s value is neither exactly 0 nor exactly 85, then the command shall fail with a status code of CONSTRAINT_ERROR.\n  - If the length of the field\u2019s value is exactly 0, then the VIDVerificationStatement field in the Fabrics attribute entry associated with the accessing fabric index shall be erased and the field shall disappear from the Fabrics entry.\n  - If the length of the field\u2019s value is exactly 85, then the VIDVerificationStatement field in the Fabrics attribute entry associated with the accessing fabric index shall have its value replaced with the value from the command field.\nIf the VVSC field is present:\n  - If the length of the field\u2019s value is exactly 0, then the VVSC field in the NOCs attribute entry associated with the accessing fabric index shall be erased and the field shall disappear from the NOCs entry.\n  - If the length of the field\u2019s value is not 0, then the VVSC field in the NOCs attribute entry associated with the accessing fabric index shall have its value replaced with the value from the command field. The contents of the certificate need not be validated by the server. Clients shall validate the contents at time of use.\nIf the command was invoked within a fail-safe context after a successful AddNOC or UpdateNOC command, then the field updates shall apply to the pending update state that will be reverted if fail-safe expires prior to a CommissioningComplete command. In other words, field updates apply to the state of the Fabrics Attribute as currently visible, even for an existing fabric currently in process of being updated."
    },
    {
      tag: "command",
      name: "SignVidVerificationRequest",
      xref: "core\xA711.18.6.15",
      details: "This command is used to authenticate the fabric associated with the FabricIndex.\nThis command shall be used to request that the server authenticate the fabric associated with the FabricIndex given by generating the response described in Section 6.4.10, \u201CFabric Table Vendor ID Verification Procedure\u201D.\nThe FabricIndex field shall contain the fabric index being targeted by the request.\nThe ClientChallenge field shall contain a client-provided random challenge to be used during the signature procedure.\n### Effect on Receipt\nIf the FabricIndex field contains a fabric index which does not have an associated entry in the Fabrics attribute, then the command shall fail with a status code of CONSTRAINT_ERROR.\nOtherwise, if no other errors have occurred, the command shall generate a SignVIDVerificationResponse."
    },
    {
      tag: "command",
      name: "SignVidVerificationResponse",
      xref: "core\xA711.18.6.16",
      details: "This command is used to report the results of the SignVIDVerificationRequest command. This command shall contain the response of the SignVIDVerificationRequest, computed as described below.\nThe FabricIndex field shall contain the same value of FabricIndex as the value from the associated SignVIDVerificationRequest.\nThe FabricBindingVersion field shall contain value 0x01 for version 1.0 of the Matter Cryptographic Primitives.\nThe Signature field shall contain the octet string result of CryptoSign(noc_private_key, vendor_id_verification_tbs):\n  - noc_private_key is the operational private key associated with the Node Operational Key Pair for the FabricIndex requested in the associated SignVIDVerificationRequest.\n  - vendor_id_verification_tbs := fabric_binding_version || client_challenge || attestation_challenge || fabric_index || vendor_fabric_binding_message || <vid_verification_statement>\n    - fabric_binding_version is the value from the FabricBindingVersion field of this SignVIDVerificationResponse.\n    - client_challenge is the 32-octet ClientChallenge from the SignVIDVerificationRequest.\n    - attestation_challenge is the AttestationChallenge from a CASE session, resumed CASE session, or PASE session depending on the method used to establish the current secure session context over which the response will be sent.\n    - fabric_index is the 1-octet value of FabricIndex from the SignVIDVerificationRequest.\n    - vendor_fabric_binding_message is the octet string of the vendor_fabric_binding_message defined in Section 6.4.10.1, \u201CAlgorithm\u201D.\n    - vid_verification_statement is the 85-octet (for cryptographic primitives mapping 1.0) value from the VIDVerificationStatement field of the entry in the Fabrics attribute associated with the fabric_index, if present. If there is no such field in the Fabrics attribute for the fabric_index specified, this field shall be omitted from the vendor_id_verification_tbs message."
    },
    {
      tag: "datatype",
      name: "CertificateChainTypeEnum",
      xref: "core\xA711.18.4.2",
      details: "This enumeration is used by the CertificateChainRequest command to convey which certificate from the device attestation certificate chain to transmit back to the client.",
      children: [
        { tag: "field", name: "DacCertificate", description: "Request the DER-encoded DAC certificate" },
        { tag: "field", name: "PaiCertificate", description: "Request the DER-encoded PAI certificate" }
      ]
    },
    {
      tag: "datatype",
      name: "NodeOperationalCertStatusEnum",
      xref: "core\xA711.18.4.3",
      details: "This enumeration is used by the NOCResponse common response command to convey detailed outcome of several of this cluster\u2019s operations.",
      children: [
        { tag: "field", name: "Ok", description: "OK, no error" },
        {
          tag: "field",
          name: "InvalidPublicKey",
          description: "Public Key in the NOC does not match the public key in the NOCSR"
        },
        {
          tag: "field",
          name: "InvalidNodeOpId",
          description: "The Node Operational ID in the NOC is not formatted correctly."
        },
        { tag: "field", name: "InvalidNoc", description: "Any other validation error in NOC chain" },
        {
          tag: "field",
          name: "MissingCsr",
          description: "No record of prior CSR for which this NOC could match"
        },
        { tag: "field", name: "TableFull", description: "NOCs table full, cannot add another one" },
        {
          tag: "field",
          name: "InvalidAdminSubject",
          description: "Invalid CaseAdminSubject field for an AddNOC command."
        },
        {
          tag: "field",
          name: "FabricConflict",
          description: "Trying to AddNOC instead of UpdateNOC against an existing Fabric."
        },
        { tag: "field", name: "LabelConflict", description: "Label already exists on another Fabric." },
        { tag: "field", name: "InvalidFabricIndex", description: "FabricIndex argument is invalid." }
      ]
    },
    {
      tag: "datatype",
      name: "NOCStruct",
      xref: "core\xA711.18.4.4",
      details: "This encodes a NOC chain, underpinning a commissioned Operational Identity for a given Node.\n> [!NOTE]\n> The VVSC field is mutually exclusive with the ICAC field. If the ICAC field is non-null, the VVSC field shall be omitted. If the VVSC field is present in the structure, the ICAC field shall be   null. The reason for this is to optimize storage usage, as the VID Verification Signer Certificate (VVSC) is a field that is only needed in root-per-fabric situations without ICAC present.\n> [!NOTE]\n> The Trusted Root CA Certificate (RCAC) is not included in this structure. The roots are available in the TrustedRootCertificates attribute under the same associated fabric as the one for the NOCStruct entry.",
      children: [
        {
          tag: "field",
          name: "Noc",
          xref: "core\xA711.18.4.4.1",
          details: "This field shall contain the NOC for the struct\u2019s associated fabric, encoded using Matter Certificate Encoding."
        },
        {
          tag: "field",
          name: "Icac",
          xref: "core\xA711.18.4.4.2",
          details: "This field shall contain the ICAC for the struct\u2019s associated fabric, encoded using Matter Certificate Encoding. If no ICAC is present in the chain, this field shall be set to null."
        },
        {
          tag: "field",
          name: "Vvsc",
          xref: "core\xA711.18.4.4.3",
          details: "This field shall contain the Vendor Verification Signer Certificate (VVSC) for the struct\u2019s associated fabric, encoded using Matter Certificate Encoding. If no VVSC is needed, this field shall be omitted (in that there shall NOT be a value present, not even an empty octet string). If the ICAC field is non-null, this field shall NOT be present."
        }
      ]
    },
    {
      tag: "datatype",
      name: "FabricDescriptorStruct",
      xref: "core\xA711.18.4.5",
      details: "This structure encodes a Fabric Reference for a fabric within which a given Node is currently commissioned.",
      children: [
        {
          tag: "field",
          name: "RootPublicKey",
          xref: "core\xA711.18.4.5.1",
          details: "This field shall contain the public key for the trusted root that scopes the fabric referenced by FabricIndex and its associated operational credential (see Section 6.4.5.3, \u201CTrusted Root CA Certificates\u201D). The format for the key shall be the same as that used in the ec-pub-key field of the Matter Certificate Encoding for the root in the operational certificate chain."
        },
        {
          tag: "field",
          name: "VendorId",
          xref: "core\xA711.18.4.5.2",
          details: "This field shall contain the value of VendorID associated with the fabric.\nThis value shall have been provided by the AdminVendorID value provided in the AddNOC command that led to the creation of this FabricDescriptorStruct, or the value updated via the SetVIDVerificationStatement command, whichever was last completed. The set of allowed values is defined in AdminVendorID.\nThe intent is to provide user transparency about which entities have Administer privileges on the Node.\nClients shall consider the VendorID field value to be untrustworthy until the Fabric Table Vendor ID Verification Procedure has been executed against the fabric entry having this VendorID."
        },
        {
          tag: "field",
          name: "FabricId",
          xref: "core\xA711.18.4.5.3",
          details: "This field shall contain the FabricID allocated to the fabric referenced by FabricIndex. This field shall match the value found in the matter-fabric-id field from the operational certificate providing the operational identity under this Fabric."
        },
        {
          tag: "field",
          name: "NodeId",
          xref: "core\xA711.18.4.5.4",
          details: "This field shall contain the NodeID in use within the fabric referenced by FabricIndex. This field shall match the value found in the matter-node-id field from the operational certificate providing this operational identity."
        },
        {
          tag: "field",
          name: "Label",
          xref: "core\xA711.18.4.5.5",
          details: "This field shall contain a commissioner-set label for the fabric referenced by FabricIndex. This field is set by the UpdateFabricLabel command."
        },
        {
          tag: "field",
          name: "VidVerificationStatement",
          xref: "core\xA711.18.4.5.6",
          details: "This field, if present, shall contain a previously-installed administrator-set vid_verification_statement value (see Section 6.4.10, \u201CFabric Table Vendor ID Verification Procedure\u201D) for the fabric referenced by FabricIndex. This field is set by the SetVIDVerificationStatement command."
        }
      ]
    }
  ]
});
//# sourceMappingURL=operational-credentials.resource.js.map
