Quorums
This feature allows an administrator to configure a system (or quorum) that can have multiple approvers for an operation. These approvers need to approve the operations before they can be successfully executed.
Note
If you are using connectors and direct NAE scripts, do not enable the DeleteKey and AddUserToGroup quorums.
Operations Supported by Quorums
| Operation | Authorized Group(s) for Approval | Auto-Executable |
|---|---|---|
| Deletekey | Key Admins | No |
| AddUserToGroup | User Admins | Yes |
| DownloadBackupKey [Root Domain Only] | Restore Admins and Backup Admins | No |
| RestoreBackup [Root Domain Only] | Restore Admins | No |
| DeleteDomain | Domain Admins | No |
| ManagePolicyAttachment | admin | No |
| DeletePolicy | admin | No |
| DownloadBackupKeyDomain | Domain Backup Admins and Domain Restore Admins | No |
| RestoreBackupDomain | Domain Restore Admins | No |
| DeleteClientCTE | CTE Admins | Yes |
| DeleteClientGroupCTE | CTE Admins | Yes |
| DeleteCSIStorageGroupCTE | CTE Admins | Yes |
| DeleteGuardPointCTE | CTE Admins | Yes |
| DeletePolicyCTE | CTE Admins | Yes |
| DeletePolicyElementsCTE | CTE Admins | Yes |
| DeleteProfileCTE | CTE Admins | Yes |
| UpdateClientGroupCTE | CTE Admins | Yes |
| UpdateCSIStorageGroupCTE | CTE Admins | Yes |
| UpdateGuardPointCTE | CTE Admins | Yes |
| UpdatePolicyCTE | CTE Admins | Yes |
| UpdatePolicyElementsCTE | CTE Admins | Yes |
| UpdateProfileCTE | CTE Admins | Yes |
| CreateAttachedPolicy | admin | No |
| DeleteAttachedPolicy | admin | No |
| DeleteGoogleWorkspaceCSEEndpoint | CCKM Admins | No |
| DeleteEKMEndpoint | CCKM Admins | No |
The above table defines the list of operations supported by quorums and whether they are auto-executable after approval. If auto-execution for the quorum profile is enabled for any operation, after approval, that operation will execute automatically. Hence, eliminates the need to re-trigger that operation manually. The auto_executable flag is not configurable.
The authorized group(s) for quorum approval associated with operations are configurable. To configure, refer to Updating Quorum Profile.
CTE and CTE UserSpace support CipherTrust Manager's quorum feature. Refer to the Quorum Control section for details on supported CTE and CTE UserSpace operations and resources.
Managing Quorum on Policies
The CipherTrust Manager allows you to enable quorum for:
These policies can be system policies, user policies, or quorum policies.
Once a quorum is enabled for ManagePolicyAttachment and DeletePolicy, the activation and deactivation of a quorum for any supported operation has to go through the quorum's approval process, similar to any other operation on the CipherTrust Manager.
Caution
Do not enable quorum on the ManagePolicyAttachment and DeletePolicy operations until all the CipherTrust Manager nodes in a cluster are upgraded to 2.10 or a higher version.
Note
It is recommended to enable quorum on both DeletePolicy and ManagePolicyAttachment operations together in the same order to bring the entire policy creation and deletion under quorum.
ManagePolicyAttachment
The ManagePolicyAttachment operation gives you a provision to enable a quorum for:
Creating policy attachments
Deleting policy attachments
When you activate a quorum, a policy and a policy attachment is created internally. If you want to bring activation of a quorum policy under a quorum, activate the quorum on the ManagePolicyAttachment.
DeletePolicy
The DeletePolicy operation is used to enable quorum on policy deletion. When you deactivate a quorum, a policy is deleted internally. If you want to bring deactivation of a quorum policy under a quorum, activate the quorum on the DeletePolicy action.
Refer to Enabling Quorum on ManagePolicyAttachment and DeletePolicy for more details.
Quorum Policies
To enable the quorum for any operation, first you need to activate the quorum policy. After the quorum policy is active for an operation, a quorum gets created in a pre-active state on performing the corresponding operation. To activate a quorum policy, refer to Activating the Quorum Policy.
For more details on quorum policies, refer to Managing Quorums Policies using ksctl.
Quorum Profile
It's a configuration that defines the expiration time, number of approvals, and the voter groups for a quorum. For more details on quorum profile, refer to Managing Quorums Profiles using ksctl.
States & Life-cycle of a Quorum Request
If an administrator has configured a quorum for any operation and the user initiates that operation, then that operation is denied and leads to creation of a quorum request.
The quorum request life-cycle is as follows:
The quorum is created in a
pre-activestate. A quorum or a quorum request can have one of these six states at a time as depicted in the below diagram.
Note
The user/requester of this quorum must activate the quorum before any of the approvers can review the quorum request.
Once the quorum is in the
activestate, it is available to the approvers to review it. The user/requester can optionally add a reason for initiating the request while activating it.When the required approvals are granted, the quorum is set to an
approvedstate.A quorum request is set to an
executedstate if the operation has been completed with an approved quorum.A deny vote forces a quorum to be in a
deniedstate implying that the operation can not be performed and the quorum is terminated.
In case, if a quorum already exists for the same operation, the status of the existing quorum is used to determine the outcome of the operation. Any approver can vote either to approve or deny a quorum request. A note can be added with the vote for additional information.
Note
A quorum in a pre-active state is prone to an expedited expiry. It expires after 15 minutes of creation, if not activated.
Note
Every quorum expires after seven (7) days of the creation and this leads to the termination of that quorum.
Managing Quorums Policies using ksctl
The following operations can be performed:
Activate the quorum policy
Get status of the quorum policy
Deactivate the quorum policy
Activating the Quorum Policy
To create a policy supporting quorum and activating the policy, run:
Syntax
ksctl quorum-policy activate --actions <Actions>
Example Request 1
ksctl quorum-policy activate --actions "DeleteKey"
Example Response
{
"Policy": {
"id": "fd6f911b-f280-492c-9eac-aed35590d530",
"uri": "kylo:kylo:admin:policies:enablequorum-fd6f911b-f280-492c-9eac-aed35590d530",
"account": "kylo:kylo:admin:accounts:kylo",
"application": "ncryptify:gemalto:admin:apps:kylo",
"devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
"createdAt": "2021-06-01T04:45:48.917228Z",
"name": "EnableQuorum",
"actions": [
"DeleteKey"
],
"resources": null,
"allow": false,
"effect": "obligate_on_allow",
"conditions": [
{
"path": "context.principal.cust.groups",
"op": "contains",
"negate": true
}
],
"updatedAt": "2023-06-01T10:11:11.000186Z"
},
"required_approvals": 2
}
Getting Status of the Quorum Policy
To know whether the quorum policy is in active state or inactive state, run:
Syntax
ksctl quorum-policy status
Example Request
ksctl quorum-policy status
Example Response
[
{
"operation": [
"AddUserToGroup"
],
"active": false,
"profile": "AddUserToGroup requires quorum"
},
{
"operation": [
"DeleteCSIStorageGroupCTE"
],
"active": false,
"profile": "DeleteCSIStorageGroupCTE requires quorum"
},
{
"operation": [
"DeleteClientCTE"
],
"active": true,
"profile": "DeleteClientCTE requires quorum"
},
{
"operation": [
"DeleteClientGroupCTE"
],
"active": true,
"profile": "DeleteClientGroupCTE requires quorum"
},
{
"operation": [
"DeleteDomain"
],
"active": false,
"profile": "DeleteDomain requires quorum"
},
{
"operation": [
"DeleteEKMEndpoint"
],
"active": false,
"profile": "DeleteEKMEndpoint requires quorum"
},
{
"operation": [
"DeleteGoogleWorkspaceCSEEndpoint"
],
"active": false,
"profile": "DeleteGoogleWorkspaceCSEEndpoint requires quorum"
},
{
"operation": [
"DeleteGuardPointCTE"
],
"active": true,
"profile": "DeleteGuardPointCTE requires quorum"
},
{
"operation": [
"DeleteKey"
],
"active": false,
"profile": "DeleteKey requires quorum"
},
{
"operation": [
"DeletePolicy"
],
"active": true,
"profile": "DeletePolicy requires quorum"
},
{
"operation": [
"DeletePolicyCTE"
],
"active": true,
"profile": "DeletePolicyCTE requires quorum"
},
{
"operation": [
"DeletePolicyElementsCTE"
],
"active": true,
"profile": "DeletePolicyElementsCTE requires quorum"
},
{
"operation": [
"DeleteProfileCTE"
],
"active": false,
"profile": "DeleteProfileCTE requires quorum"
},
{
"operation": [
"DownloadBackupkey"
],
"active": false,
"profile": "DownloadBackupkey requires quorum"
},
{
"operation": [
"DownloadBackupkeyDomain"
],
"active": false,
"profile": "DownloadBackupkeyDomain requires quorum"
},
{
"operation": [
"ManagePolicyAttachment"
],
"active": false,
"profile": "ManagePolicyAttachment requires quorum"
},
{
"operation": [
"RestoreBackup"
],
"active": false,
"profile": "RestoreBackup requires quorum"
},
{
"operation": [
"RestoreBackupDomain"
],
"active": false,
"profile": "RestoreBackupDomain requires quorum"
},
{
"operation": [
"UpdateCSIStorageGroupCTE"
],
"active": false,
"profile": "UpdateCSIStorageGroupCTE requires quorum"
},
{
"operation": [
"UpdateClientGroupCTE"
],
"active": true,
"profile": "UpdateClientGroupCTE requires quorum"
},
{
"operation": [
"UpdateGuardPointCTE"
],
"active": true,
"profile": "UpdateGuardPointCTE requires quorum"
},
{
"operation": [
"UpdatePolicyCTE"
],
"active": true,
"profile": "UpdatePolicyCTE requires quorum"
},
{
"operation": [
"UpdatePolicyElementsCTE"
],
"active": true,
"profile": "UpdatePolicyElementsCTE requires quorum"
},
{
"operation": [
"UpdateProfileCTE"
],
"active": true,
"profile": "UpdateProfileCTE requires quorum"
}
]
The 'active' field represents whether policy is active. It returns true if the quorum policy is active and false otherwise.
Deactivating the Quorum Policy
To deactivate the already active quorum policy for any specific operation, run:
Syntax
ksctl quorum-policy deactivate --actions <Actions>
Example Request
ksctl quorum-policy deactivate "DeleteKey"
Example Response
There will be no response if quorum policy is deactivated successfully.
Enabling Quorum on ManagePolicyAttachment and DeletePolicy
Enabling a quorum on ManagePolicyAttachment and DeletePolicy brings activation/deactivation of a quorum policy under a quorum. It implies that you won't be able to activate/deactivate any quorum on your own without creating a quorum for that request.
Let's consider a scenario where you have activated a quorum for the "DeleteKey" operation. Currently, you are allowed to deactivate the created quorum.
However, if a quorum is enabled on ManagePolicyAttachment and DeletePolicy, you cannot activate/deactivate any quorum.
Now, let's enable a quorum on both ManagePolicyAttachment and DeletePolicy operations. To do so, run the following commands:
For ManagePolicyAttachment
ksctl quorum-policy activate --actions "ManagePolicyAttachment"
Response
{
"Policy": {
"id": "865baeb0-cace-4e76-943c-3fea78c0252d",
"uri": "kylo:kylo:admin:policies:managepolicyattachment-requires-quorum-865baeb0-cace-4e76-943c-3fea78c0252d",
"account": "kylo:kylo:admin:accounts:kylo",
"application": "ncryptify:gemalto:admin:apps:kylo",
"devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
"createdAt": "2022-09-08T11:05:48.488623Z",
"name": "ManagePolicyAttachment requires quorum",
"actions": [
"CreateAttachedPolicy",
"DeleteAttachedPolicy"
],
"resources": null,
"allow": false,
"effect": "obligate_on_allow",
"conditions": [
{
"path": "context.principal.cust.groups",
"op": "contains",
"negate": true
}
],
"updatedAt": "2023-06-01T10:18:59.469775Z"
},
"required_approvals": 3
}
For DeletePolicy
ksctl quorum-policy activate --actions "DeletePolicy"
Response
{
"Policy": {
"id": "e735b3e8-4698-45ad-814a-4ddfad75c572",
"uri": "kylo:kylo:admin:policies:deletepolicy-requires-quorum-e735b3e8-4698-45ad-814a-4ddfad75c572",
"account": "kylo:kylo:admin:accounts:kylo",
"application": "ncryptify:gemalto:admin:apps:kylo",
"devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
"createdAt": "2022-09-08T11:05:45.325665Z",
"name": "DeletePolicy requires quorum",
"actions": [
"DeletePolicy"
],
"resources": null,
"allow": false,
"effect": "obligate_on_allow",
"conditions": [
{
"path": "context.principal.cust.groups",
"op": "contains",
"negate": true
}
],
"updatedAt": "2023-06-01T10:19:39.524036Z"
},
"required_approvals": 3
}
Now, if you try to deactivate the quorum for "DeleteKey" created above, an error is thrown as shown below and the deactivation of quorum is not allowed:
{
"code": 4,
"codeDesc": "NCERRInsufficientPermissions",
"message": "A Quorum has been created with ID (fd6f911b-f280-492c-9eac-aed35590d530) in pre-active state. Please activate it."
}
Managing Quorums using ksctl
The following operations can be performed:
Activate quorum
Approve quorum
Deny quorum
List/Search quorums
Get quorum
Delete quorum
Revoke vote
Activating Quorums
To activate a quorum, run:
Syntax
ksctl quorum activate --id <QuorumId> --quorum-reason <Reason-to-activate>
It changes the state of the quorum from pre-active to active. A quorum can be approved only when it is in the active state.
After quorum is active, it is available for the approval process.
Example Request
ksctl quorum activate --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
Example Response
{
"id": "558622f8-bf20-4ded-9f43-e72bfaaf73a5",
"uri": "kylo:kylo:sallyport:quorum:558622f8-bf20-4ded-9f43-e72bfaaf73a5",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-06-01T10:25:21.691222Z",
"updatedAt": "2023-06-01T10:26:02.944903Z",
"requester_id": "local|2e8bcf46-dcba-4f5f-89d2-8ea16c7c305f",
"requester_username": "admin",
"operation_fingerprint": "872a47b84aae3c37e2c966e135b931fcf6642fc23bc7df6cbc3c27eeae759546",
"operation": "DeleteKey",
"resource_uri": "kylo:kylo:vault:keys:test123-v0",
"state": "active",
"required_approvals": 3,
"meta": null,
"votes": [],
"auto_executable": false
}
Note
The requester of the operation is also the owner of the associated quorum. Only the requester/owner has permission to activate the associated quorum.
Approving Quorums
To approve a quorum, run:
Syntax
ksctl quorum approve --id <QuorumId> --note <Additional-note-for-approval>
When all the required approvals are available, then quorum moves to the approved state and you can re-initiate the associated operation.
Example Request
ksctl quorum approve --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
Example Response
There will be no response if quorum is approved successfully.
Denying Quorums
To deny a approval to a quorum, run:
Syntax
ksctl quorum deny --id <QuorumId> --note <Additional-note-for-denial>
This command moves a quorum to the denied state. This is a terminal state and quorum is unusable after deny.
Example Request
ksctl quorum deny --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
Example Response
There will be no response if quorum is denied successfully.
Getting List of Quorums
To get the list of quorums, run:
Syntax
ksctl quorum list
Example Request
ksctl quorum list
Example Response
{
"skip": 0,
"limit": 10,
"total": 1,
"resources": [
{
"id": "9c9d0fd8-7b0b-4ce6-a464-0bf9202b0922",
"uri": "kylo:kylo:sallyport:quorum:9c9d0fd8-7b0b-4ce6-a464-0bf9202b0922",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-06-01T10:19:39.572608Z",
"updatedAt": "2023-06-01T10:19:39.571465Z",
"requester_id": "local|2e8bcf46-dcba-4f5f-89d2-8ea16c7c305f",
"requester_username": "admin",
"operation_fingerprint": "d57025a50105185e51a4e277859bb1246105cbfcd67dd25b59212d890487ee07",
"operation": "CreateAttachedPolicy",
"resource_uri": "kylo:kylo:admin:policy-attachments:f15ee123-7874-4819-9be3-e78fbee4a41c",
"state": "pre-active",
"required_approvals": 3,
"meta": null,
"votes": [],
"auto_executable": false
}
]
}
Getting Details of Quorums
To get details of a quorum, run:
Syntax
ksctl quorum get --id <QuorumId>
Example Request
ksctl quorum get --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
Example Response
{
"id": "558622f8-bf20-4ded-9f43-e72bfaaf73a5",
"uri": "kylo:kylo:sallyport:quorum:558622f8-bf20-4ded-9f43-e72bfaaf73a5",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-06-01T10:25:21.691222Z",
"updatedAt": "2023-06-01T10:26:02.944903Z",
"requester_id": "local|2e8bcf46-dcba-4f5f-89d2-8ea16c7c305f",
"operation_fingerprint": "872a47b84aae3c37e2c966e135b931fcf6642fc23bc7df6cbc3c27eeae759546",
"operation": "DeleteKey",
"resource_uri": "kylo:kylo:vault:keys:test123-v0",
"state": "active",
"required_approvals": 1,
"meta": null,
"votes": []
}
Deleting Quorums
To delete a quorum, run:
Syntax
ksctl quorum delete --id <QuorumId>
Example Request
ksctl quorum delete --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
There will be no response if quorum is deleted successfully.
Note
The requester of the operation is the owner of the associated quorum. Only the requester/owner has permission to delete the quorum.
Revoking Vote for Quorums
To revoke your vote from an already approved quorum, run:
Syntax
ksctl quorum revoke --id <QuorumId>
If the number of approvals falls below the required approvals, the quorum moves back to the active state.
Example Request
ksctl quorum revoke --id 558622f8-bf20-4ded-9f43-e72bfaaf73a5
Example Response
There will be no response if vote is revoked successfully.
Managing Quorum Profiles using ksctl
The following operations can be performed:
Get quorum profile
List/Search quorum profiles
Update quorum profile
Getting Details of the Quorum Profile
To get the details of quorum profile, run:
Syntax
ksctl quorum-profiles get --profile-id <ProfileID>
Example Request
ksctl quorum-profiles get --profile-id "0e75ff2e-0d76-4681-98d3-cb3e42d5a4de"
Example Response
{
"id": "0e75ff2e-0d76-4681-98d3-cb3e42d5a4de",
"uri": "kylo:kylo:sallyport:quorum-profile:deletekey-requires-quorum-0e75ff2e-0d76-4681-98d3-cb3e42d5a4de",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.038906Z",
"updatedAt": "2023-06-05T04:19:00.095912Z",
"name": "Deletekey requires quorum",
"required_approvals": 3,
"voter_groups": [
"Key Admins"
],
"excluded_groups": [
"Key Users"
]
}
Getting List of Quorum Profiles
To get the list of all quorum profiles, run:
Syntax
ksctl quorum-profiles list
Example Request
ksctl quorum-profiles list
Example Response
{
"skip": 0,
"limit": 10,
"total": 28,
"resources": [
{
"id": "bf16fb8e-1e19-4875-9c78-7f2dd50a0a2d",
"uri": "kylo:kylo:sallyport:quorum-profile:updateprofilecte-requires-quorum-bf16fb8e-1e19-4875-9c78-7f2dd50a0a2d",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.000799Z",
"updatedAt": "2023-05-31T10:11:38.000197Z",
"name": "UpdateProfileCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "f929da9f-dc19-4c1f-871c-0f69fe5a3371",
"uri": "kylo:kylo:sallyport:quorum-profile:updatepolicyelementscte-requires-quorum-f929da9f-dc19-4c1f-871c-0f69fe5a3371",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.014439Z",
"updatedAt": "2023-05-31T10:11:38.013891Z",
"name": "UpdatePolicyElementsCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "cc8def90-b3fe-42e0-bc2c-bc1ea7be6eee",
"uri": "kylo:kylo:sallyport:quorum-profile:updatepolicycte-requires-quorum-cc8def90-b3fe-42e0-bc2c-bc1ea7be6eee",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:37.950185Z",
"updatedAt": "2023-05-31T10:11:37.949144Z",
"name": "UpdatePolicyCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "308ff9fd-ce83-4bef-94e6-2e6f2e9cb88e",
"uri": "kylo:kylo:sallyport:quorum-profile:updateguardpointcte-requires-quorum-308ff9fd-ce83-4bef-94e6-2e6f2e9cb88e",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:37.976519Z",
"updatedAt": "2023-05-31T10:11:37.970618Z",
"name": "UpdateGuardPointCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "b0e0c715-f931-46fd-81dd-254a024ad88e",
"uri": "kylo:kylo:sallyport:quorum-profile:updatecsistoragegroupcte-requires-quorum-b0e0c715-f931-46fd-81dd-254a024ad88e",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:37.953287Z",
"updatedAt": "2023-05-31T10:11:37.952172Z",
"name": "UpdateCSIStorageGroupCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "6a83aadf-b9a6-4cf4-b351-68719257d6ff",
"uri": "kylo:kylo:sallyport:quorum-profile:updateclientgroupcte-requires-quorum-6a83aadf-b9a6-4cf4-b351-68719257d6ff",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:37.968485Z",
"updatedAt": "2023-05-31T10:11:37.967915Z",
"name": "UpdateClientGroupCTE requires quorum",
"required_approvals": 3,
"voter_groups": [
"CTE Admins"
],
"excluded_groups": null
},
{
"id": "fdcce1c4-2c89-479a-ad75-51e5e95a70fc",
"uri": "kylo:kylo:sallyport:quorum-profile:restorebackup-requires-quorum-fdcce1c4-2c89-479a-ad75-51e5e95a70fc",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.026042Z",
"updatedAt": "2023-05-31T10:11:38.018999Z",
"name": "RestoreBackup requires quorum",
"required_approvals": 3,
"voter_groups": [
"Restore Admins"
],
"excluded_groups": null
},
{
"id": "02e0f0c6-5071-4b08-8296-de89c5e8aa08",
"uri": "kylo:kylo:sallyport:quorum-profile:restorebackupdomain-requires-quorum-02e0f0c6-5071-4b08-8296-de89c5e8aa08",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.005456Z",
"updatedAt": "2023-05-31T10:11:38.004807Z",
"name": "RestoreBackupDomain requires quorum",
"required_approvals": 3,
"voter_groups": [
"Domain Restore Admins"
],
"excluded_groups": null
},
{
"id": "bd52de83-6611-4aaa-a9f3-bd344c66923d",
"uri": "kylo:kylo:sallyport:quorum-profile:managepolicyattachment-requires-quorum-bd52de83-6611-4aaa-a9f3-bd344c66923d",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.007084Z",
"updatedAt": "2023-05-31T10:11:38.006579Z",
"name": "ManagePolicyAttachment requires quorum",
"required_approvals": 3,
"voter_groups": [
"admin"
],
"excluded_groups": null
}
]
}
Updating Quorum Profile
You can update the quorum profile for the following fields:
approvals- the number of approvals (votes) required to move the quorum to the Approved state.voter-groups- the groups defined in the voter-groups field are allowed to vote for this profile. The users part of these groups can either approve or deny a quorum request.excluded-groups- the groups defined in the excluded-groups field are excluded from being a part of the quorum for the operation specified in the quorum profile. The quorum policies will not apply to all the users associated with the groups specified in the excluded_groups field. Let's take a scenario where the "group1" group is added to the list of excluded-groups. If user "user1" is part of a group "group1", then quorum policies won't apply to the "user1".
To update the quorum profile, run:
Syntax
ksctl quorum-profiles update --profile-id <ProfileID> --approvals <NumberOfApprovals> --voter-groups <VoterGroups> --excluded-groups <List-of-Excluded-Groups>
Example Request 1
ksctl quorum-profiles update --profile-id 61af169c-36b7-42b8-b396-284b92a52613 --approvals 2
Example Response 1 (Update for approvals)
{
"id": "61af169c-36b7-42b8-b396-284b92a52613",
"uri": "kylo:kylo:sallyport:quorum-profile:managepolicy-requires-quorum-61af169c-36b7-42b8-b396-284b92a52613",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2021-08-20T05:15:50.329875Z",
"updatedAt": "2021-08-20T05:19:32.613434Z",
"name": "ManagePolicy requires quorum",
"required_approvals": 2,
"voter_groups": [
"admin"
]
}
In the above example, two (2) approvals are required to move the quorum to the Approved state.
Example Request 2 (Update for voter groups)
ksctl quorum-profiles update --profile-id 61af169c-36b7-42b8-b396-284b92a52613 --approvals 2 --voter-groups 'Domain Admins,Key Admins'
Example Response 2
{
"id": "61af169c-36b7-42b8-b396-284b92a52613",
"uri": "kylo:kylo:sallyport:quorum-profile:managepolicy-requires-quorum-61af169c-36b7-42b8-b396-284b92a52613",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2021-08-20T05:15:50.329875Z",
"updatedAt": "2021-08-20T05:19:32.613434Z",
"name": "ManagePolicy requires quorum",
"required_approvals": 2,
"voter_groups": [
"Domain Admins"
"Key Admins"
]
}
In the above example, only the "Domain Admins" and "Key Admins" groups are allowed to vote for this profile.
Example Request 3 (Update for excluded groups)
ksctl quorum-profiles update --profile-id "0e75ff2e-0d76-4681-98d3-cb3e42d5a4de" --excluded-groups "Key Users"
Example Response 3
{
"id": "0e75ff2e-0d76-4681-98d3-cb3e42d5a4de",
"uri": "kylo:kylo:sallyport:quorum-profile:updatekey-requires-quorum-0e75ff2e-0d76-4681-98d3-cb3e42d5a4de",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2023-05-31T10:11:38.038906Z",
"updatedAt": "2023-06-05T04:19:00.095912Z",
"name": "UpdateKey requires quorum",
"required_approvals": 3,
"voter_groups": [
"Key Admins"
],
"excluded_groups": [
"Key Users"
]
}
In the above example, the users added to the "Key Users" groups are excluded from being a part of the quorum for the "UpdateKey requires quorum" operation.
