Repository navigation
[DigiCert] 2FA will be turned on for your account #3453
Description
Activity
For which workflow do we need it?
My fault, @RafaelGSS 🤦♂️. I will transfer the issue to the build team
FWIW this account is, I believe, used for the current Windows Authenticode code-signing certificate (see #2415). The certificate itself, as well as update instructions, is stashed in the secrets repo under
build/releasewith the account username/password in the usual admin logins file underbuild/infra.As an aside our current certificate expires in December this year. From the Node.js 20.5.0 Windows binary:
@richardlau while you were in there, could you tell if we can get the 2FA seed so that we can store in screts so all appropriate build team members can get access?
@mhdawson I've never attempted to log into the account.
@bensternthal can you confirm this is not the same account that was used to create our new certificates? The email was sent to build@iojs.org.
@mhdawson I checked both DigiCert and DigiCert One and we did not create any accounts with the build@iojs.org. We started from scratch. So the account referenced in this thread is not related to the new certificates.
Logged in and set up 2FA - https://github.com/nodejs-private/secrets/pull/297 adds the info people will need to set up 2fa as well.
This is the account we used for the last microsoft signing certificate which expires in ~30 days. After that we probably don't need the account anymore as the new certificate was generated out of an account managed by the OpenJS Foundation.
@bensternthal thanks for confirming.
New email arrived. topic:
[Security Announcement] Two-Factor Authentication will be turned on for your account. Seems like we need to do some manual actionsContext
Next steps