The security multi-admin-verify request show-pending command displays information about multi-admin verification requests that are in the pending state.

Parameters

{ [-fields <fieldname>,…]: If you specify the -fields <fieldname>, … parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.
| [-instance ] }: If you specify the -instance parameter, the command displays detailed information about all fields.
[-index <integer>] - Request Index: This specifies the index of the request.
[-operation <text>] - Operation: This specifies the ONTAP operation for which the request is created.
[-query <query>] - Query: This identifies the object (or objects) upon which the user wants to apply the operation.
[-required-approvers <integer>] - Required Approvers: This specifies the number of distinct users that are required to approve the request. A user can set the required-approvers to the ONTAP operation rule. If a user does not set the required-approvers to the rule, then the required-approvers from the global setting is applied.
[-pending-approvers <integer>] - Pending Approvers: This specifies the number of distinct users that are still required to approve the request for the request to be marked as approved.
[-approval-expiry {MM/DD/YYYY HH:MM:SS | {1..7}days | {1..168}hours | PnDTnHnMnS | PnW}] - Approval Expiry: This specifies the expiry information within which an approve or veto action is to be taken by the approvers from the time the request is submitted. Any authorized user can set the approval-expiry to the ONTAP operation rule. If the user does not set the approval-expiry to the rule, then the approval-expiry from the global setting is applied.
[-execution-expiry {MM/DD/YYYY HH:MM:SS | {1..7}days | {1..168}hours | PnDTnHnMnS | PnW}] - Execution Expiry: This specifies the expiry information within which an ONTAP operation is to be executed from the time the request is approved. An authoried user can set the execution-expiry to the ONTAP operation rule. If the user does not set the execution-expiry to the rule, then the execution-expiry from the global setting is applied.
[-users-approved <text>,…] - Approvals: This specifies the list of users that have approved the request.
[-user-vetoed <text>] - User Vetoed: This specifies the user who vetoed the request.
[-vserver <vserver>] - Vserver: This specifies the Vserver information to which the request is associated with.
[-user-requested <text>] - User Requested: This specifies the username who created the request.
[-time-created <MM/DD/YYYY HH:MM:SS>] - Time Created: This specifies the time at which the request is created.
[-time-approved <MM/DD/YYYY HH:MM:SS>] - Time Approved: This specifies the time at which the request state changed to approved.
[-comment <text>] - Comment: This specifies the comments that are associated with the request.
[-users-permitted <text>,…] - Users Permitted: This specifies the list of users that are permitted to perform the ONTAP operation for which the request is approved. If users-permitted is empty, then any user who, by default, has permission to perform the ONTAP operation is allowed.
[-execute-on-approval {true|false}] - Execute Approved Command: This specifies whether the operation being approved is automatically executed. If set, the operation is executed immediately when the request is is marked as approved.

Examples

The following example displays typical request information:

cluster1::> security multi-admin-verify request show-pending
Pending
    Index Operation              Query                   State    Approvers Requestor
    ----- ---------------------- ----------------------- -------- --------- ---------
        1 volume delete                                  pending  3         admin