An active signing request requires immediate action due to the strict 100-second time limit. The approval workflow is dynamically determined by the security policy associated with the certificate's Environment Name.
If the policy for the associated Environment Name requires Multi-Factor Authentication (MFA) for approval, the process involves two distinct steps, providing the highest level of assurance.
1. MFA Validation Required: The request first appears with the Approval Status as Pending and the Actions column shows Requires MFA.
2. MFA Code Submission: Clicking Requires MFA triggers the system to send a one-time MFA code to your registered email. A pop-up then asks you to enter the one-time password.
3. Action Buttons Appear: Once you validate your identity with the correct MFA code, the request status is updated, and the full approval action buttons— Approve and Deny—will appear, allowing you to finalize the request.
If the policy for the certificate's Environment Name does not require MFA, you are immediately presented with the final decision options.
1. Direct Action: The active request appears with the Approval Status as Pending, and the Actions column displays the Approve and Deny buttons directly.
2. Finalizing the Request: Clicking Approve sends the authorization back to the signing job, updates the status to Approved, and changes the action to Request Completed. Clicking Deny updates the status to Rejected. If the approver doesn't take any action, the request will get timed out and the action button will disappear.
Note: If you don't see a new request or the status hasn't updated, just hit the refresh button.