Skip to content

Commit ba6dd1b

Browse files
fixing metadata.json
1 parent 4903293 commit ba6dd1b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/trusted-signing/how-to-signing-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,11 +74,11 @@ Complete these steps to download and install the Trusted Signing Dlib package (.
7474
### Create JSON file
7575
To sign using Trusted Signing, you need to provide the details of your Trusted Signing Account and Certificate Profile that were created as part of the prerequisites. You provide this information on a JSON file by completing these steps:
7676
1. Create a new JSON file (for example `metadata.json`).
77-
2. Add the specific values for your Trusted Signing Account and Certificate Profile to the JSON file. For more information, see the metadata.sample.json file that’s included in the Trusted Signing Dlib package or refer to the following example:
77+
2. Add the specific values for your Trusted Signing Account and Certificate Profile to the JSON file. The Trusted Signing Account is also interchangeably called Code Signing Account. For more information, see the metadata.sample.json file that’s included in the Trusted Signing Dlib package or refer to the following example:
7878
```
7979
{
8080
  "Endpoint": "<Trusted Signing Account Endpoint>",
81-
  "TrustedSigningAccountName": "<Trusted Signing Account Name>",
81+
  "CodeSigningAccountName": "<Trusted Signing Account Name>",
8282
  "CertificateProfileName": "<Certificate Profile Name>",
8383
  "CorrelationId": "<Optional CorrelationId*>"
8484
}

0 commit comments

Comments
 (0)