mirror of https://github.com/dapr/docs.git
Merge branch 'v1.9' into endgame_v1.9
This commit is contained in:
commit
0383b2f8d3
|
@ -304,11 +304,13 @@ Run the `order-processor` service alongside a Dapr sidecar.
|
||||||
dapr run --app-port 7001 --app-id order-processor --app-protocol http --dapr-http-port 3501 -- dotnet run
|
dapr run --app-port 7001 --app-id order-processor --app-protocol http --dapr-http-port 3501 -- dotnet run
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Below is the working code block from the order processor's `Program.cs` file.
|
||||||
|
|
||||||
```csharp
|
```csharp
|
||||||
app.MapPost("/orders", async context => {
|
app.MapPost("/orders", (Order order) =>
|
||||||
var data = await context.Request.ReadFromJsonAsync<Order>();
|
{
|
||||||
Console.WriteLine("Order received : " + data);
|
Console.WriteLine("Order received : " + order);
|
||||||
await context.Response.WriteAsync(data.ToString());
|
return order.ToString();
|
||||||
});
|
});
|
||||||
```
|
```
|
||||||
|
|
||||||
|
@ -334,7 +336,7 @@ Run the `checkout` service alongside a Dapr sidecar.
|
||||||
dapr run --app-id checkout --app-protocol http --dapr-http-port 3500 -- dotnet run
|
dapr run --app-id checkout --app-protocol http --dapr-http-port 3500 -- dotnet run
|
||||||
```
|
```
|
||||||
|
|
||||||
In the `checkout` service, you'll notice there's no need to rewrite your app code to use Dapr's service invocation. You can enable service invocation by simply adding the `dapr-app-id` header, which specifies the ID of the target service.
|
In the Program.cs file for the `checkout` service, you'll notice there's no need to rewrite your app code to use Dapr's service invocation. You can enable service invocation by simply adding the `dapr-app-id` header, which specifies the ID of the target service.
|
||||||
|
|
||||||
```csharp
|
```csharp
|
||||||
var client = new HttpClient();
|
var client = new HttpClient();
|
||||||
|
|
|
@ -447,7 +447,7 @@ Tell the Sentry service where to load the certificates from using the `--issuer-
|
||||||
|
|
||||||
The next examples creates root and issuer certs and loads them with the Sentry service.
|
The next examples creates root and issuer certs and loads them with the Sentry service.
|
||||||
|
|
||||||
*Note: This example uses the step tool to create the certificates. You can install step tool from [here](https://smallstep.com/docs/getting-started/). Windows binaries available [here](https://github.com/smallstep/cli/releases)*
|
*Note: This example uses the step tool to create the certificates. You can install step tool from [here](https://smallstep.com/docs/step-cli/installation). Windows binaries available [here](https://github.com/smallstep/cli/releases)*
|
||||||
|
|
||||||
Create the root certificate:
|
Create the root certificate:
|
||||||
|
|
||||||
|
|
|
@ -12,7 +12,7 @@ When the middleware is enabled any method invocation through Dapr needs to be au
|
||||||
|
|
||||||
The main difference between the two flows is that the `Authorization Code Grant flow` needs user interaction and authorizes a user where the `Client Credentials Grant flow` doesn't need a user interaction and authorizes a service/application.
|
The main difference between the two flows is that the `Authorization Code Grant flow` needs user interaction and authorizes a user where the `Client Credentials Grant flow` doesn't need a user interaction and authorizes a service/application.
|
||||||
|
|
||||||
## Register your application with a authorization server
|
## Register your application with an authorization server
|
||||||
|
|
||||||
Different authorization servers provide different application registration experiences. Here are some samples:
|
Different authorization servers provide different application registration experiences. Here are some samples:
|
||||||
<!-- IGNORE_LINKS -->
|
<!-- IGNORE_LINKS -->
|
||||||
|
|
Loading…
Reference in New Issue