Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 6b1bba9

Browse files
authoredJun 7, 2022
Apply suggestions from code review
Made changes per acrolinx scorecard
1 parent ade896a commit 6b1bba9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎articles/attestation/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@
7878
href: https://search.maven.org/artifact/com.azure/azure-security-attestation/1.1.2/jar
7979
- name: Python data-plane SDK
8080
href: https://pypi.org/project/azure-security-attestation/
81-
- name: Javascript SDK
81+
- name: JavaScript SDK
8282
href: https://www.npmjs.com/package/@azure/attestation/v/1.0.0
8383
- name: Azure PowerShell
8484
href: /powershell/module/az.attestation/#attestation

‎articles/attestation/workflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Here are the general steps in a typical TPM enclave attestation workflow (using
4141

4242
1. On device/platform boot, various boot loaders and boot services measure events backed by TPM and securely store them as TCG logs. Client collects the TCG logs from the device and TPM quote which acts evidence for attestation
4343
2. The client authenticates to Azure AD and obtains a access token
44-
3. The client has an URI which refers to an instance of Azure Attestation. The client sends the evidence and the Azure Active Directory (AAD) access token to Azure Attestation. Exact information submitted to the provider depends on the platform
44+
3. The client has an URI which refers to an instance of Azure Attestation. The client sends the evidence and the Azure Active Directory (Azure AD) access token to Azure Attestation. Exact information submitted to the provider depends on the platform
4545
4. Azure Attestation validates the submitted information and evaluates it against a configured policy. If the verification succeeds, Azure Attestation issues an attestation token and returns it to the client. If this step fails, Azure Attestation reports an error to the client. The communication between the client and attestation service is dictated by the Azure attestation TPM protocol
4646
5. The client then sends the attestation token to relying party. The relying party calls public key metadata endpoint of Azure Attestation to retrieve signing certificates. The relying party then verifies the signature of the attestation token and ensures the platforms trustworthiness
4747

0 commit comments

Comments
 (0)
Please sign in to comment.