mirror of https://github.com/dapr/docs.git
Merge branch 'mfussell-sec-patch' of https://github.com/msfussell/docs into mfussell-sec-patch
Signed-off-by: Mark Fussell <markfussell@gmail.com>
This commit is contained in:
commit
512bb88a90
|
@ -333,7 +333,7 @@ Restart your sidecar and try retrieving state again to observe that state persis
|
|||
Begin by launching a Dapr sidecar:
|
||||
|
||||
```bash
|
||||
dapr --app-id orderprocessing --port 3601 run
|
||||
dapr --app-id orderprocessing --dapr-http-port 3601 run
|
||||
```
|
||||
|
||||
Then in a separate terminal save a key/value pair into your statestore:
|
||||
|
|
|
@ -65,7 +65,7 @@ Run the following command to launch a Dapr sidecar that will listen on port 3500
|
|||
dapr run --app-id myapp --dapr-http-port 3500 --components-path ./my-components
|
||||
```
|
||||
|
||||
> If you encounter a error message stating the app ID is already in use, it may be that the sidecar you ran in the previous step is still running. Make sure you stop the sidecar before running the above command (e.g. using "Control-C").
|
||||
> If you encounter a error message stating the app ID is already in use, it may be that the sidecar you ran in the previous step is still running. Make sure you stop the sidecar before running the above command using "Control-C" or running the command `dapr stop --app-id myapp`.
|
||||
|
||||
## Step 4: Get a secret
|
||||
|
||||
|
|
|
@ -15,7 +15,7 @@ The main difference between the two flows is that the `Authorization Code Grant
|
|||
## Register your application with a authorization server
|
||||
|
||||
Different authorization servers provide different application registration experiences. Here are some samples:
|
||||
|
||||
<!-- IGNORE_LINKS -->
|
||||
* [Azure AAD](https://docs.microsoft.com/azure/active-directory/develop/v1-protocols-oauth-code)
|
||||
* [Facebook](https://developers.facebook.com/apps)
|
||||
* [Fitbit](https://dev.fitbit.com/build/reference/web-api/oauth2/)
|
||||
|
@ -23,7 +23,7 @@ Different authorization servers provide different application registration exper
|
|||
* [Google APIs](https://console.developers.google.com/apis/credentials/consen)
|
||||
* [Slack](https://api.slack.com/docs/oauth)
|
||||
* [Twitter](http://apps.twitter.com/)
|
||||
|
||||
<!-- END_IGNORE -->
|
||||
To figure the Dapr OAuth middleware, you'll need to collect the following information:
|
||||
|
||||
* Client ID (see [here](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/))
|
||||
|
|
|
@ -45,7 +45,7 @@ spec:
|
|||
# - name: defaultMessageTimeToLiveInSec # Optional
|
||||
# value: 10
|
||||
# - name: autoDeleteOnIdleInSec # Optional
|
||||
# value: 10
|
||||
# value: 3600
|
||||
# - name: maxReconnectionAttempts # Optional
|
||||
# value: 30
|
||||
# - name: connectionRecoveryInSec # Optional
|
||||
|
@ -78,7 +78,7 @@ The above example uses secrets as plain strings. It is recommended to use a secr
|
|||
| maxConcurrentHandlers | N |Defines the maximum number of concurrent message handlers | `10`
|
||||
| prefetchCount | N |Defines the number of prefetched messages (use for high throughput / low latency scenarios)| `5`
|
||||
| defaultMessageTimeToLiveInSec | N |Default message time to live. | `10`
|
||||
| autoDeleteOnIdleInSec | N |Time in seconds to wait before auto deleting messages. | `10`
|
||||
| autoDeleteOnIdleInSec | N |Time in seconds to wait before auto deleting idle subscriptions. | `3600`
|
||||
| maxReconnectionAttempts | N |Defines the maximum number of reconnect attempts. Default: `30` | `30`
|
||||
| connectionRecoveryInSec | N |Time in seconds to wait between connection recovery attempts. Defaults: `2` | `2`
|
||||
| publishMaxRetries | N | The max number of retries for when Azure Service Bus responds with "too busy" in order to throttle messages. Defaults: `5` | `5`
|
||||
|
|
|
@ -92,7 +92,7 @@ You can then interact with the server using the client port: `localhost:4222`.
|
|||
{{% /codetab %}}
|
||||
|
||||
{{% codetab %}}
|
||||
Install NATS on Kubernetes by using the [kubectl](https://docs.nats.io/running-a-nats-service/introduction/running/nats-kubernetes/minimal-setup#minimal-nats-setup):
|
||||
Install NATS on Kubernetes by using the [kubectl](https://docs.nats.io/running-a-nats-service/introduction/running/nats-kubernetes/):
|
||||
|
||||
```bash
|
||||
# Single server NATS
|
||||
|
|
Loading…
Reference in New Issue