Skip to content

Cm 70024 cli update certificates - #515

Closed
omer-roth wants to merge 6 commits into
mainfrom
CM-70024-cli-update-certificates
Closed

Cm 70024 cli update certificates#515
omer-roth wants to merge 6 commits into
mainfrom
CM-70024-cli-update-certificates

Conversation

@omer-roth

Copy link
Copy Markdown
Collaborator

No description provided.

omer-roth and others added 6 commits August 2, 2026 14:46
DigiCert issued a new Cycode Ltd code signing cert (valid 2026-06-05 to
2027-08-22). Point signtool at its thumbprint via the temporary
SM_CODE_SIGNING_CERT_SHA1_HASH_NEW secret so the old value stays intact
as a fallback until a CI run confirms the new cert signs successfully.

Also drop --keypair-alias from certsync. The previous attempt failed with
"Certificate for keypair alias: *** not found", which synced zero certs
and left signtool with no candidates. Syncing every cert in the account
and letting /sha1 pick removes an extra value to keep in sync on renewal.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
certsync without an alias only synced the first keypair the account
returns (the old cert), so signtool still had no match for the new
thumbprint. Restore --keypair-alias, sourced from SM_KEYPAIR_ALIAS_NEW.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The keypair is visible in the KSP but smctl reports its certificate as
not found. List keypairs and certificates in CI to see the association
and status. To be removed before merge.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Drop the probe steps now that the new cert signs. Point the client cert,
its password and the API key at _NEW secrets so a service account can be
verified in CI without disturbing main, and keep a temporary healthcheck
to confirm which identity actually signs.

Also record why certsync failed for the new cert: it only syncs keypairs
the calling identity may sign with, so the credential owner must be a
signer on the certificate.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The cert rotation itself lives entirely in DigiCert One and the repo
secrets, so all _NEW indirection is gone. What is worth keeping in the
workflow is why certsync reported the new certificate as missing: it
only syncs keypairs the calling identity may sign with.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@omer-roth
omer-roth requested a review from avishaiamiel as a code owner August 2, 2026 12:50

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

@omer-roth omer-roth closed this Aug 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant