Skip to content

Commit b373bc9

Browse files
committed
Updates
1 parent 990a129 commit b373bc9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/attestation/troubleshoot-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ In order to manage policies, an Azure AD user requires the following permissions
5252
In order to read policies, an Azure AD user requires the following permission for "Actions":
5353
- Microsoft.Attestation/attestationProviders/attestation/read
5454

55-
To perform this action, an Azure AD user must have "Attestation Reader" role on the attestation provider. The read permission can be also be inherited with roles such as "Reader" (wildcard permissions) on the subscription/ resource group.
55+
To perform this action, an Azure AD user must have "Attestation Reader" role on the attestation provider. The read permissions can be also be inherited with roles such as "Reader" (wildcard permissions) on the subscription/ resource group.
5656

5757
To verify the roles in PowerShell, run the below steps:
5858

articles/attestation/workflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Here are the general steps in a typical TPM enclave attestation workflow (using
4242
2. The client authenticates to Azure AD and obtains an access token.
4343
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.
4444
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.
45-
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
45+
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 platform's trustworthiness.
4646

4747
![TPM validation flow](./media/tpm-validation-flow.png)
4848

0 commit comments

Comments
 (0)