|
3 | 3 | metadata:
|
4 | 4 | title: Trusted Signing FAQ
|
5 | 5 | description: Get answers to frequently asked questions about Trusted Signing.
|
6 |
| - author: microsoftshawarma |
7 |
| - ms.author: rakiasegev |
| 6 | + author: TacoTechSharma |
| 7 | + ms.author: mesharm |
8 | 8 | ms.service: trusted-signing
|
9 | 9 | ms.topic: faq
|
10 | 10 | ms.date: 03/18/2024
|
@@ -35,11 +35,20 @@ sections:
|
35 | 35 |
|
36 | 36 | :::image type="content" source="media/trusted-signing-resource-provider.png" alt-text="Screenshot of registering the Microsoft.CodeSigning resource provider." lightbox="media/trusted-signing-resource-provider.png":::
|
37 | 37 |
|
38 |
| - - question: What if identity validation fails? |
| 38 | + - question: What if Organization identity validation fails? |
39 | 39 | answer: |
|
40 | 40 | - Currently, an organization that has a year-founded date of less than three years can't be onboarded, and identity validation fails.
|
41 | 41 | - If your organization has a year-founded date of more than three years, ensure that you didn't miss an email verification link that was sent to the primary email address you entered when you created your identity validation request. The link expires after seven days. If you overlooked the email or if you didn't select the link in the email within seven days, create a new identity validation request.
|
42 | 42 | - If identity validation fails, but not because of a missed email verification, the Microsoft validation team wasn't able to make a determination about your request based on the information that you provided. Even if you provide more documentation when we request it, if we can't validate the information, we can't onboard you to Trusted Signing. In this scenario, we recommend that you delete your Trusted Signing account so that you aren't billed for unused resources.
|
| 43 | + - question: For Individual identity validation, what if I don’t have an address on a bank statement or utility bill? |
| 44 | + answer: | |
| 45 | + Be sure to use a government issued ID with address on it, in order to successfully go through the process. |
| 46 | + - question: For Individual identity validation, I see an error - "You do not have permission to access this page". |
| 47 | + answer: | |
| 48 | + Verify you are using the same email address to access the Identity Validation link, that you entered in the Identity Validation request. |
| 49 | + - question: What if I already have a VID? |
| 50 | + answer: | |
| 51 | + Follow the steps to present your existing VID for Trusted Signing. For this process, VIDs must include your address in addition to your name. Ensure that your VIDs have your address on them before using them for Trusted Signing. |
43 | 52 | - question: What if I need assistance with identity validation?
|
44 | 53 | answer: |
|
45 | 54 | For questions about identity validation in Trusted Signing, contact us by using [Microsoft Q&A](https://learn.microsoft.com/answers/tags/509/trusted-signing) (use the tag **Azure Trusted Signing**) or [Stack Overflow](https://stackoverflow.com/questions/tagged/trusted-signing) (use the tag **trusted-signing**). Azure support doesn't resolve identity validation issues for Trusted Signing.
|
@@ -107,11 +116,11 @@ sections:
|
107 | 116 | - question: How do I fix pop-up credentials in an Azure virtual machine when I run the SignTool + dlib command?
|
108 | 117 | answer: |
|
109 | 118 | 1. Create a [user-assigned managed identity](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview).
|
110 |
| - 1. Add the user-assigned managed identity to the VM: |
| 119 | + 2. Add the user-assigned managed identity to the VM: |
111 | 120 | 1. Select the VM.
|
112 |
| - 1. On the left menu, select **Identity**, and then select **User assigned**. |
113 |
| - 1. Select **Add** to add the managed identity. |
114 |
| - 1. In the resource group (or subscription) that has the Trusted Signing Certificate Profile Signer role, add the user-assigned managed identity to the role. To assign the correct role, go to **Access control (IAM)** > **Role assignments**. |
| 121 | + 2. On the left menu, select **Identity**, and then select **User assigned**. |
| 122 | + 3. Select **Add** to add the managed identity. |
| 123 | + 3. In the resource group (or subscription) that has the Trusted Signing Certificate Profile Signer role, add the user-assigned managed identity to the role. To assign the correct role, go to **Access control (IAM)** > **Role assignments**. |
115 | 124 | - question: How do I fix pop-up credentials when I use Google Cloud Platform?
|
116 | 125 | answer: |
|
117 | 126 | - Because Google Cloud Platform (GCP) doesn't have an Azure managed identity resource by default, set up an [environment credential](https://docs.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet). Use the [EnvironmentCredential class](https://docs.microsoft.com/dotnet/api/azure.identity.environmentcredential?view=azure-dotnet) to set up the credential. We recommend that you use these variables:
|
|
0 commit comments