Skip to content

Commit

Permalink
Update README.md to remove confusion about API Key in Intel Tiber Tru…
Browse files Browse the repository at this point in the history
…st Services (#274)

This commit is made to clearly specify that the API Key in Step 9 is Attestation API Key, so that someone doesn't continue with Admin API Key which comes ahead in the tutorial provided. Making this correction from personal experience.
  • Loading branch information
npankaj365 authored Nov 15, 2024
1 parent 5c3ac23 commit 8547de6
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -534,15 +534,15 @@ you proceed to [step 4](#verify-itts-client-version).
3. Attest with the [Intel Tiber Trust Service](https://www.intel.com/content/www/us/en/security/trust-authority.html).
1. Subscribe to the Intel Tiber Trust Service [free trial](https://plan.seek.intel.com/2023_ITATrialForm).
2. Obtain an API key following this [tutorial](https://docs.trustauthority.intel.com/main/articles/tutorial-api-key.html?tabs=attestation-api-key-portal%2Cattestation-sgx-client).
2. Obtain an Attestation API key following this [tutorial](https://docs.trustauthority.intel.com/main/articles/tutorial-api-key.html?tabs=attestation-api-key-portal%2Cattestation-sgx-client).
3. Create a `config.json` file like the example below:
```console
{
"trustauthority_url": "https://portal.trustauthority.intel.com",
"trustauthority_api_url": "https://api.trustauthority.intel.com",
"trustauthority_api_key": "<Your Intel Tiber Trust Service API key>"
"trustauthority_api_key": "<Your Intel Tiber Trust Service Attestation API key>"
}
```
Expand Down

0 comments on commit 8547de6

Please sign in to comment.