Skip to content

Commit 4fcff36

Browse files
committed
1-2-3 ZeroConfig fix
1 parent efc35e7 commit 4fcff36

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

articles/active-directory/verifiable-credentials/admin-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -545,7 +545,7 @@ Although it is technically possible to publish multiple domains, we currently on
545545

546546
### Well-known DID configuration
547547

548-
The `generateWellknownDidConfiguration` method generates the signed did-configuration.json file. The file must be uploaded to the `.well-known` folder in the root of the website hosted for the domain in the linked domain of this verifiable credential instance. Instructions can be found [here](how-to-dnsbind.md#distribute-well-known-config).
548+
The `generateWellknownDidConfiguration` method generates the signed did-configuration.json file. The file must be uploaded to the `.well-known` folder in the root of the website hosted for the domain in the linked domain of this verifiable credential instance. Instructions can be found [here](how-to-dnsbind.md#verify-domain-ownership-and-distribute-did-configuration.json-file).
549549

550550
#### HTTP request
551551

articles/active-directory/verifiable-credentials/how-to-dnsbind.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ To verify domain ownership to your DID, you need to have completed the following
2424

2525
- Complete the [Getting Started](get-started-verifiable-credentials.md) and subsequent [tutorial set](enable-your-tenant-verifiable-credentials.md).
2626

27-
## Verify domain ownership and distribute .well-known/did-configuration.json file
27+
## Verify domain ownership and distribute did-configuration.json file
2828

2929
The domain you will verify ownership of to your DID is defined in the organizational settings.
3030

articles/active-directory/verifiable-credentials/how-to-register-didwebsite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The DID document in the `did.json` file needs to be republished if you changed t
5050

5151
## How can I verify that the registration is working?
5252

53-
The portal verifies that the `did.json` is reachable and correct when you click the [**Refresh registration status** button](#how-do-i-register-my-website-id). You should also consider verifying that you can request that URL in a browser to avoid errors like not using https, a bad SSL certificate or the URL not being public. If the `did.json` file cannot be requested anonymously in a browser or via tools such as `curl`, without warnings or errors, the portal will not be able to complete the **Refresh registration status** step either.
53+
The portal verifies that the `did.json` is reachable and correct when you click the **Refresh registration status** button. You should also consider verifying that you can request that URL in a browser to avoid errors like not using https, a bad SSL certificate or the URL not being public. If the `did.json` file cannot be requested anonymously in a browser or via tools such as `curl`, without warnings or errors, the portal will not be able to complete the **Refresh registration status** step either.
5454

5555
>[!NOTE]
5656
> If you are experiencing problems refreshing your registration status, you can troubleshoot it via running `curl -Iv https://yourdomain.com/.well-known/did.json` on an machine with Ubuntu OS. Windows Subsystem for Linux with Ubuntu will work too. If curl fails, refreshing the registration status will not work.

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ After you create your key vault, Verifiable Credentials generates a set of keys
6767

6868
## Set up Verified ID
6969

70-
:::image type="content" source="media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started.png" alt-text="Screenshot that shows how to set up Verifiable Credentials.":::
70+
:::image type="content" source="media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started.png" alt-text="Screenshot that shows how to set up Verifiable Credentials.":::
7171

7272
To set up Verified ID, follow these steps:
7373

@@ -161,7 +161,7 @@ You can choose to grant issuance and presentation permissions separately if you
161161

162162
After Azure Key Vault is setup, and the service have a signing key, you must complete step 2 and 3 in the setup.
163163

164-
:::image type="content" source="media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started-step-2-3.png" alt-text="Screenshot that shows how to set up Verifiable Credentials step 2 and 3.":::
164+
:::image type="content" source="media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started-step-2-3.png" alt-text="Screenshot that shows how to set up Verifiable Credentials step 2 and 3.":::
165165

166166
1. Navigate to the Verified ID service in the Azure portal.
167167
1. From the left menu, select **Setup**.

0 commit comments

Comments
 (0)