Skip to content

Commit

Permalink
fix broken links (#24098)
Browse files Browse the repository at this point in the history
  • Loading branch information
gewarren committed May 10, 2021
1 parent 5beded2 commit 4c7afea
Show file tree
Hide file tree
Showing 9 changed files with 12 additions and 12 deletions.
2 changes: 1 addition & 1 deletion docs/architecture/dapr-for-net-developers/observability.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ spec:

##### Inspect the telemetry in Zipkin

Once the application is started, the Dapr sidecars will emit telemetry to the Zipkin server. To inspect this telemetry, point a web-browser to <http://localhost:32411>. You'll see the Zipkin web front end:
Once the application is started, the Dapr sidecars will emit telemetry to the Zipkin server. To inspect this telemetry, point a web-browser to `http://localhost:32411`. You'll see the Zipkin web front end:

![The Zipkin start page](media/observability/zipkin.png)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ In the next section, you'll learn how to build a DevOps pipeline with Azure Pipe
## Additional reading

* [Web Apps overview](/azure/app-service/app-service-web-overview)
* [Build a .NET Core and SQL Database web app in Azure App Service](/azure/app-service/app-service-web-tutorial-dotnetcore-sqldb)
* [Build a .NET Core and SQL Database web app in Azure App Service](/azure/app-service/tutorial-dotnetcore-sqldb-app)
* [Configure deployment credentials for Azure App Service](/azure/app-service/app-service-deployment-credentials)
* [Set up staging environments in Azure App Service](/azure/app-service/web-sites-staged-publishing)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -394,7 +394,7 @@ In the case of the "Marketing" business area and microservices, it is a simple u

### Authentication and authorization in Ocelot API Gateways

In an Ocelot API Gateway you can sit the authentication service, such as an ASP.NET Core Web API service using [IdentityServer](https://identityserver.io/) providing the auth token, either out or inside the API Gateway.
In an Ocelot API Gateway, you can sit the authentication service, such as an ASP.NET Core Web API service using [IdentityServer](../../cloud-native/identity-server.md) providing the auth token, either out or inside the API Gateway.

Since eShopOnContainers is using multiple API Gateways with boundaries based on BFF and business areas, the Identity/Auth service is left out of the API Gateways, as highlighted in yellow in the following diagram.

Expand Down
4 changes: 2 additions & 2 deletions docs/azure/includes/dotnet-all.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
| Event Hubs - Schema Registry | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.Data.SchemaRegistry/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/Data.SchemaRegistry-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Data.SchemaRegistry_1.0.0-beta.2/sdk/schemaregistry/Azure.Data.SchemaRegistry/) |
| Form Recognizer | NuGet [3.0.1](https://www.nuget.org/packages/Azure.AI.FormRecognizer/3.0.1)<br>NuGet [3.1.0-beta.4](https://www.nuget.org/packages/Azure.AI.FormRecognizer/3.1.0-beta.4) | [docs](/dotnet/api/overview/azure/AI.FormRecognizer-readme/) | GitHub [3.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.FormRecognizer_3.0.1/sdk/formrecognizer/Azure.AI.FormRecognizer/)<br>GitHub [3.1.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.FormRecognizer_3.1.0-beta.4/sdk/formrecognizer/Azure.AI.FormRecognizer/) |
| Identity | NuGet [1.3.0](https://www.nuget.org/packages/Azure.Identity/1.3.0)<br>NuGet [1.4.0-beta.5](https://www.nuget.org/packages/Azure.Identity/1.4.0-beta.5) | [docs](/dotnet/api/overview/azure/Identity-readme/) | GitHub [1.3.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Identity_1.3.0/sdk/identity/Azure.Identity/)<br>GitHub [1.4.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Identity_1.4.0-beta.5/sdk/identity/Azure.Identity/) |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.IoT.DeviceUpdate_item.Version/sdk/deviceupdate/Azure.Iot.DeviceUpdate/) |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/deviceupdate/Azure.IoT.DeviceUpdate) |
| Key Vault - Administration | NuGet [4.0.0-beta.4](https://www.nuget.org/packages/Azure.Security.KeyVault.Administration/4.0.0-beta.4) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Administration-readme-pre/) | GitHub [4.0.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Administration_4.0.0-beta.4/sdk/keyvault/Azure.Security.KeyVault.Administration/) |
| Key Vault - Certificates | NuGet [4.1.1](https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates/4.1.1)<br>NuGet [4.2.0-beta.5](https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates/4.2.0-beta.5) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Certificates-readme/) | GitHub [4.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Certificates_4.1.1/sdk/keyvault/Azure.Security.KeyVault.Certificates/)<br>GitHub [4.2.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Certificates_4.2.0-beta.5/sdk/keyvault/Azure.Security.KeyVault.Certificates/) |
| Key Vault - Keys | NuGet [4.1.1](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.1.1)<br>NuGet [4.2.0-beta.5](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.2.0-beta.5) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Keys-readme/) | GitHub [4.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.1.1/sdk/keyvault/Azure.Security.KeyVault.Keys/)<br>GitHub [4.2.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.2.0-beta.5/sdk/keyvault/Azure.Security.KeyVault.Keys/) |
Expand Down Expand Up @@ -202,7 +202,7 @@
| Image Search | NuGet [2.0.0](https://www.nuget.org/packages/Microsoft.Azure.CognitiveServices.Search.ImageSearch/2.0.0) | | |
| Information Protection | NuGet [1.7.147](https://www.nuget.org/packages/Microsoft.InformationProtection.File/1.7.147) | | |
| Insights | NuGet [0.16.0-preview](https://www.nuget.org/packages/Microsoft.Azure.Insights/0.16.0-preview) | | |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.IoT.DeviceUpdate_item.Version/sdk/deviceupdate/Azure.Iot.DeviceUpdate/) |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/deviceupdate/Azure.IoT.DeviceUpdate) |
| Jobs | NuGet [0.3.2-beta](https://www.nuget.org/packages/Microsoft.Azure.Jobs/0.3.2-beta) | | GitHub [0.3.2-beta](https://github.com/Azure/azure-webjobs-sdk) |
| Jobs - Core | NuGet [0.3.2-beta](https://www.nuget.org/packages/Microsoft.Azure.Jobs.Core/0.3.2-beta) | | GitHub [0.3.2-beta](https://github.com/Azure/azure-webjobs-sdk) |
| Jobs - Service Bus | NuGet [0.3.2-beta](https://www.nuget.org/packages/Microsoft.Azure.Jobs.ServiceBus/0.3.2-beta) | | GitHub [0.3.2-beta](https://github.com/Azure/azure-webjobs-sdk) |
Expand Down
2 changes: 1 addition & 1 deletion docs/azure/includes/dotnet-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
| Event Hubs - Schema Registry | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.Data.SchemaRegistry/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/Data.SchemaRegistry-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Data.SchemaRegistry_1.0.0-beta.2/sdk/schemaregistry/Azure.Data.SchemaRegistry/) |
| Form Recognizer | NuGet [3.0.1](https://www.nuget.org/packages/Azure.AI.FormRecognizer/3.0.1)<br>NuGet [3.1.0-beta.4](https://www.nuget.org/packages/Azure.AI.FormRecognizer/3.1.0-beta.4) | [docs](/dotnet/api/overview/azure/AI.FormRecognizer-readme/) | GitHub [3.0.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.FormRecognizer_3.0.1/sdk/formrecognizer/Azure.AI.FormRecognizer/)<br>GitHub [3.1.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.FormRecognizer_3.1.0-beta.4/sdk/formrecognizer/Azure.AI.FormRecognizer/) |
| Identity | NuGet [1.3.0](https://www.nuget.org/packages/Azure.Identity/1.3.0)<br>NuGet [1.4.0-beta.5](https://www.nuget.org/packages/Azure.Identity/1.4.0-beta.5) | [docs](/dotnet/api/overview/azure/Identity-readme/) | GitHub [1.3.0](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Identity_1.3.0/sdk/identity/Azure.Identity/)<br>GitHub [1.4.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Identity_1.4.0-beta.5/sdk/identity/Azure.Identity/) |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/Azure.IoT.DeviceUpdate_item.Version/sdk/deviceupdate/Azure.Iot.DeviceUpdate/) |
| IoT Device Update | NuGet [1.0.0-beta.2](https://www.nuget.org/packages/Azure.IoT.DeviceUpdate/1.0.0-beta.2) | [docs](/dotnet/api/overview/azure/IoT.DeviceUpdate-readme-pre/) | GitHub [1.0.0-beta.2](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/deviceupdate/Azure.IoT.DeviceUpdate) |
| Key Vault - Administration | NuGet [4.0.0-beta.4](https://www.nuget.org/packages/Azure.Security.KeyVault.Administration/4.0.0-beta.4) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Administration-readme-pre/) | GitHub [4.0.0-beta.4](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Administration_4.0.0-beta.4/sdk/keyvault/Azure.Security.KeyVault.Administration/) |
| Key Vault - Certificates | NuGet [4.1.1](https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates/4.1.1)<br>NuGet [4.2.0-beta.5](https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates/4.2.0-beta.5) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Certificates-readme/) | GitHub [4.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Certificates_4.1.1/sdk/keyvault/Azure.Security.KeyVault.Certificates/)<br>GitHub [4.2.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Certificates_4.2.0-beta.5/sdk/keyvault/Azure.Security.KeyVault.Certificates/) |
| Key Vault - Keys | NuGet [4.1.1](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.1.1)<br>NuGet [4.2.0-beta.5](https://www.nuget.org/packages/Azure.Security.KeyVault.Keys/4.2.0-beta.5) | [docs](/dotnet/api/overview/azure/Security.KeyVault.Keys-readme/) | GitHub [4.1.1](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.1.1/sdk/keyvault/Azure.Security.KeyVault.Keys/)<br>GitHub [4.2.0-beta.5](https://github.com/Azure/azure-sdk-for-net/tree/Azure.Security.KeyVault.Keys_4.2.0-beta.5/sdk/keyvault/Azure.Security.KeyVault.Keys/) |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ dotnet dev-certs https --clean

### With PowerShell

You can use PowerShell to generate self-signed certificates. The [PKI Client](/powershell/module/pkiclient/new-selfsignedcertificate?preserve-view=true&view=win10-ps) can be used to generate a self-signed certificate.
You can use PowerShell to generate self-signed certificates. The [PKI Client](/powershell/module/pki/new-selfsignedcertificate) can be used to generate a self-signed certificate.

```powershell
$cert = New-SelfSignedCertificate -DnsName @("contoso.com", "www.contoso.com") -CertStoreLocation "cert:\LocalMachine\My"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,12 @@ ms.assetid: bc5f6637-5513-4d27-99bb-51aad7741e4a
---
# How to: Create Temporary Certificates for Use During Development

When developing a secure service or client using Windows Communication Foundation (WCF), it is often necessary to supply an X.509 certificate to be used as a credential. The certificate typically is part of a chain of certificates with a root authority found in the Trusted Root Certification Authorities store of the computer. Having a certificate chain enables you to scope a set of certificates where typically the root authority is from your organization or business unit. To emulate this at development time, you can create two certificates to satisfy the security requirements. The first is a self-signed certificate that is placed in the Trusted Root Certification Authorities store, and the second certificate is created from the first and is placed in either the Personal store of the Local Machine location, or the Personal store of the Current User location. This topic walks through the steps to create these two certificates using the PowerShell [New-SelfSignedCertificate)](/powershell/module/pkiclient/new-selfsignedcertificate) cmdlet.
When developing a secure service or client using Windows Communication Foundation (WCF), it is often necessary to supply an X.509 certificate to be used as a credential. The certificate typically is part of a chain of certificates with a root authority found in the Trusted Root Certification Authorities store of the computer. Having a certificate chain enables you to scope a set of certificates where typically the root authority is from your organization or business unit. To emulate this at development time, you can create two certificates to satisfy the security requirements. The first is a self-signed certificate that is placed in the Trusted Root Certification Authorities store, and the second certificate is created from the first and is placed in either the Personal store of the Local Machine location, or the Personal store of the Current User location. This topic walks through the steps to create these two certificates using the PowerShell [New-SelfSignedCertificate)](/powershell/module/pki/new-selfsignedcertificate) cmdlet.

> [!IMPORTANT]
> The certificates that the New-SelfSignedCertificate cmdlet generates are provided for testing purposes only. When deploying a service or client, be sure to use an appropriate certificate provided by a certification authority. This could either be from a Windows Server certificate server in your organization or a third party.
>
> By default, the [New-SelfSignedCertificate](/powershell/module/pkiclient/new-selfsignedcertificate) cmdlet creates certificates that are self-signed and these certificates are insecure. Placing the self-signed certificates in the Trusted Root Certification Authorities store enables you to create a development environment that more closely simulates your deployment environment.
> By default, the [New-SelfSignedCertificate](/powershell/module/pki/new-selfsignedcertificate) cmdlet creates certificates that are self-signed and these certificates are insecure. Placing the self-signed certificates in the Trusted Root Certification Authorities store enables you to create a development environment that more closely simulates your deployment environment.
For more information about creating and using certificates, see [Working with Certificates](working-with-certificates.md). For more information about using a certificate as a credential, see [Securing Services and Clients](securing-services-and-clients.md). For a tutorial about using Microsoft Authenticode technology, see [Authenticode Overviews and Tutorials](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms537360(v=vs.85)).

Expand All @@ -26,7 +26,7 @@ The following command creates a self-signed certificate with a subject name of "
$rootCert = New-SelfSignedCertificate -CertStoreLocation Cert:\CurrentUser\My -DnsName "RootCA" -TextExtension @("2.5.29.19={text}CA=true") -KeyUsage CertSign,CrlSign,DigitalSignature
```

We need to export the certificate to a PFX file so that it can be imported to where it's needed in a later step. When exporting a certificate with the private key, a password is needed to protect it. We save the password in a `SecureString` and use the [Export-PfxCertificate](/powershell/module/pkiclient/export-pfxcertificate) cmdlet to export the certificate with the associated private key to a PFX file. We also save just the public certificate into a CRT file using the [Export-Certificate](/powershell/module/pkiclient/export-certificate) cmdlet.
We need to export the certificate to a PFX file so that it can be imported to where it's needed in a later step. When exporting a certificate with the private key, a password is needed to protect it. We save the password in a `SecureString` and use the [Export-PfxCertificate](/powershell/module/pki/export-pfxcertificate) cmdlet to export the certificate with the associated private key to a PFX file. We also save just the public certificate into a CRT file using the [Export-Certificate](/powershell/module/pki/export-certificate) cmdlet.

```powershell
[System.Security.SecureString]$rootCertPassword = ConvertTo-SecureString -String "password" -Force -AsPlainText
Expand Down
2 changes: 1 addition & 1 deletion docs/standard/data/sqlite/dapper-limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Describes some of the limitations you will encounter when using Dap
---
# Dapper limitations

There are a few limitations you should be aware of when using Microsoft.Data.Sqlite with [Dapper](https://stackexchange.github.io/Dapper/).
There are a few limitations you should be aware of when using Microsoft.Data.Sqlite with [Dapper](https://github.com/DapperLib/Dapper).

## Parameters

Expand Down
2 changes: 1 addition & 1 deletion docs/whats-new/2021-02.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ The following people contributed to the .NET docs during this period. Thank you!
- [nschonni](https://github.com/nschonni) - Nick Schonning (1)
- [parelkobra](https://github.com/parelkobra) - David Ruiz (1)
- [pavel-mikula-sonarsource](https://github.com/pavel-mikula-sonarsource) - Pavel Mikula (1)
- [realcooltrev](https://github.com/realcooltrev) - Trevor Pierce (1)
- [realcooltrev](https://github.com/ketchup-cfg) - Trevor Pierce (1)
- [rgwood](https://github.com/rgwood) - Reilly Wood (1)
- [robbell](https://github.com/robbell) - Rob Bell (1)
- [RyanLiu99](https://github.com/RyanLiu99) - Ryan Liu (1)
Expand Down

0 comments on commit 4c7afea

Please sign in to comment.