GitLab Software Trust Manager (STM) 統合 -KSP

To register the KSP, open a command prompt and run:

smksp_registrar.exe register

To verify that your KSP is configured properly, and that your client can properly authenticate to the DigiCert​​®​​ Software Trust Manager service, run:

certutil.exe -csp "DigiCert Software Trust Manager KSP" -key -user

For the client tools to access the private keys in the service through the Key Storage Provider (KSP), your certificates must be synchronized to the local certificate store. Only if the certificate is synchronized, the private key remains stored securely in DigiCert​​®​​ Software Trust Manager.

To synchronize your certificates to the local certificate store, open a command prompt and run:

smksp_cert_sync.exe

To view the certificates, open Certificate Manager for the user account used to run the certificate sync utility:

certmgr.msc

If you do not see your certificates in the Certificate Manager, verify that you have opened the correct certificate store. There is a different certificate store for each Windows user account.

Operating systems use the environment variable called PATH to determine where executable files are stored on your system. Use the PATH environment variable to store the file path to your signing tools to ensure that the CLI can reference these signing tools.

set PATH=%path%;<path to DigiCert One Signing Manager Tools>

set PATH=%path%;C:\Program Files\DigiCert\DigiCert One Signing Manager Tools

The API token is an authentication method used to verify you as a user and your permissions assigned in DigiCert ONE. The API token provides the first factor authentication.

Follow these steps to generate an API token:

The client authentication certificate is an authentication method used to verify you as a user and your permissions assigned in DigiCert ONE. The client authentication certificate provides the second factor authentication.

Follow these steps to create a client authentication certificate:

証明書付きの RSA テスト鍵ペアを生成する GitLab CI/CD 操作の例：

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
      & $SSM\smctl.exe keypair generate rsa <keypair name> --cert-alias=<certificate name> --cert-profile-id=<certificate profile id> --generate-cert=true --key-type=TEST

証明書付きの RSA プロダクション鍵ペアを生成する GitLab CI/CD パイプラインのステップの例：

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
          & $SSM\smctl.exe keypair generate rsa <keypair name> --cert-alias=<certificate name> --cert-profile-id=<certificate profile id> --generate-cert=true --key-type=PRODUCTION

パラメータは前の場合と同じですが、プロファイルカテゴリが「プロダクション」である証明書プロファイルを選択していることを確認してください。

An example of a GitLab CI/CD step to generate a certificate for an existing keypair:

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
       & $SSM\smctl.exe keypair generate-cert <keypair id> --cert-alias=<certificate name> --cert-profile-id=<certificate profile id>

To sign with SignTool:

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
          & $SIGNTOOL sign /sha1 <certificate thumbprint> /tr http://timestamp.digicert.com /td SHA256 /fd SHA256 <file to be signed>

The input parameters are the thumbprint of the certificate to be used for signing and the path to the .exe or .dll to be signed.

To sign with Mage:

Signing using nuget.exe:
stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
           nuget sign <package folder> -Timestamper http://timestamp.digicert.com -outputdirectory <output folder> -Certificate Fingerprint <SHA1 Thumbprint> -HashAlgorithm SHA256 -Verbosity detailed -Overwrite

The inputs to this task are the path to the package and the thumbprint of the certificate. The certificate thumbprint on can be identified on the certificate details page in DigiCert ONE portal.

To verify a signature with Mage:

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
           & $MAGE -Verify <Path to signed .application file>

The only input required here is the path to the signed .application file.

To verify a signature with NuGet:

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
           nuget verify -All <output folder>\*

The only input required here is the path to the signed folder.

To verify a signature with SignTool:

stages:
  - set-SM-certificate

set_SM_certificate:
  stage: set-SM-certificate
  tags:  
  - shared-windows
  - windows
  - windows-1809

  script:
    - |
           & $SIGNTOOL verify /v /pa <Path to the signed .exe or .dll>

The only input for this step is the path to the signed .exe or .dll that needs to be verified.