Managing GitLab key uploads
When an Environment's template uses a Git Signing Connector, the Environment's Instances tab shows whether each user's GPG signing key was uploaded to GitLab. From this tab, you can upload failed keys again or revoke keys in GitLab.
To view upload status
- Click Projects, and then open the Project that contains the Environment.
- Click the Environments tab, and then open the Environment.
- In the Environment details pane, click Instances.
These columns appear only when the Environment's template uses a Git Signing Connector:
- GitLab Upload: the upload status of each signing key. The Info column shows each key's type. Encryption and authentication keys aren't uploaded and show a dash.
- Key Fingerprint: the fingerprint of the key that was last uploaded to GitLab, or a dash if no key has been uploaded yet. You can compare it with the fingerprint shown in the user's GitLab account.
|
Status |
Meaning |
|
Uploaded |
The public key is in the user's GitLab account. |
|
Pending |
The upload is queued or in progress. If GitLab is temporarily unavailable, the upload is retried automatically. Keys that existed before the connector was assigned to the template stay Pending until the key is renewed or the Trust Protection Foundation service restarts. |
|
Failed |
The upload failed and won't be retried automatically. Point to the status to see the error, and see Troubleshooting GitLab key uploads. After you fix the cause, repush the key. |
|
Revoked |
The key was revoked in GitLab from this tab. |
Check boxes appear only next to keys you can act on: Failed keys can be repushed, and Uploaded keys can be revoked. The Repush Selected and Revoke Selected buttons above the table show how many of the selected keys each action applies to.
Repush failed keys
- On the Instances tab, select the keys with the Failed status.
- Click Repush Selected.
The selected keys change to Pending while they're uploaded again, and then to Uploaded when the upload succeeds. If the upload fails again, the status returns to Failed.
Revoke keys in GitLab
Revoke a key in GitLab when it should no longer be trusted, for example if it's compromised. Keys aren't revoked in GitLab automatically when they're revoked or disabled in Code Sign Manager.
CAUTION When a key is revoked in GitLab, GitLab marks all commits signed with it as unverified, including commits made before you revoked it.
- On the Instances tab, select the keys with the Uploaded status.
- Click Revoke Selected.
- In the Revoke Key(s) dialog, review the list of keys, and then click Revoke.
The keys' status changes to Revoked. The keys remain in Code Sign Manager. To stop users from signing with a key, manage it in Code Sign Manager as well.