You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/concept-dataflow-enrich.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ For example, consider the following dataset with a few records, represented as J
32
32
}
33
33
```
34
34
35
-
The mapper accesses the reference dataset stored in the Azure IoT Operations [distributed state store (DSS)](../create-edge-apps/concept-about-state-store-protocol.md) by using a key value based on a *condition* specified in the mapping configuration. Key names in the DSS correspond to a dataset in the dataflow configuration.
35
+
The mapper accesses the reference dataset stored in the Azure IoT Operations [state store](../create-edge-apps/concept-about-state-store-protocol.md) by using a key value based on a *condition* specified in the mapping configuration. Key names in the state store correspond to a dataset in the dataflow configuration.
36
36
37
37
# [Bicep](#tab/bicep)
38
38
@@ -64,7 +64,7 @@ datasets:
64
64
65
65
When a new record is being processed, the mapper performs the following steps:
66
66
67
-
* **Data request:** The mapper sends a request to the DSS to retrieve the dataset stored under the key `Position`.
67
+
* **Data request:** The mapper sends a request to the state store to retrieve the dataset stored under the key `Position`.
68
68
* **Record matching:** The mapper then queries this dataset to find the first record where the `Position` field in the dataset matches the `Position` field of the incoming record.
69
69
70
70
# [Bicep](#tab/bicep)
@@ -102,7 +102,7 @@ When a new record is being processed, the mapper performs the following steps:
102
102
103
103
---
104
104
105
-
In this example, the `WorkingHours` field is added to the output record, while the `BaseSalary` is used conditionally only when the incoming record doesn't contain the `BaseSalary` field (or the value is `null` if it's a nullable field). The request for the contextualization data doesn't happen with every incoming record. The mapper requests the dataset and then it receives notifications from DSS about the changes, while it uses a cached version of the dataset.
105
+
In this example, the `WorkingHours` field is added to the output record, while the `BaseSalary` is used conditionally only when the incoming record doesn't contain the `BaseSalary` field (or the value is `null` if it's a nullable field). The request for the contextualization data doesn't happen with every incoming record. The mapper requests the dataset and then it receives notifications from the state store about the changes, while it uses a cached version of the dataset.
106
106
107
107
It's possible to use multiple datasets:
108
108
@@ -169,7 +169,7 @@ inputs: [
169
169
170
170
---
171
171
172
-
The input references use the key of the dataset like `position` or `permission`. If the key in DSS is inconvenient to use, you can define an alias:
172
+
The input references use the key of the dataset like `position` or `permission`. If the key in state store is inconvenient to use, you can define an alias:
To enrich the data, you can use the reference dataset in the Azure IoT Operations [distributed state store (DSS)](../create-edge-apps/concept-about-state-store-protocol.md). The dataset is used to add extra data to the source data based on a condition. The condition is specified as a field in the source data that matches a field in the dataset.
512
+
To enrich the data, you can use the reference dataset in the Azure IoT Operations [state store](../create-edge-apps/concept-about-state-store-protocol.md). The dataset is used to add extra data to the source data based on a condition. The condition is specified as a field in the source data that matches a field in the dataset.
513
513
514
-
You can load sample data into the DSS by using the [DSS set tool sample](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/dss_set). Key names in the distributed state store correspond to a dataset in the dataflow configuration.
514
+
You can load sample data into the state store by using the [DSS set tool sample](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/dss_set). Key names in the state store correspond to a dataset in the dataflow configuration.
Copy file name to clipboardExpand all lines: articles/iot-operations/manage-mqtt-broker/howto-configure-authorization.md
+59-59Lines changed: 59 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.subservice: azure-mqtt-broker
7
7
ms.topic: how-to
8
8
ms.custom:
9
9
- ignite-2023
10
-
ms.date: 11/08/2024
10
+
ms.date: 11/11/2024
11
11
12
12
#CustomerIntent: As an operator, I want to configure authorization so that I have secure MQTT broker communications.
13
13
ms.service: azure-iot-operations
@@ -21,7 +21,7 @@ Authorization policies determine what actions the clients can perform on the bro
21
21
22
22
## Link BrokerAuthorization to BrokerListener
23
23
24
-
To link a *BrokerListener* to a *BrokerAuthorization* resource, specify the `authenticationRef` field in the `ports` setting of the *BrokerListener* resource. Similar to BrokerAuthentication, the *BrokerAuthorization* resource can be linked to multiple *BrokerListener* ports. The authorization policies apply to all linked listener ports. However, there's one key difference compared with BrokerAuthentication:
24
+
To link a *BrokerListener* to a *BrokerAuthorization* resource, specify the `authorizationRef` field in the `ports` setting of the *BrokerListener* resource. Similar to BrokerAuthentication, the *BrokerAuthorization* resource can be linked to multiple *BrokerListener* ports. The authorization policies apply to all linked listener ports. However, there's one key difference compared with BrokerAuthentication:
25
25
26
26
> [!IMPORTANT]
27
27
> To have the *BrokerAuthorization* configuration apply to a listener port, at least one BrokerAuthentication must also be linked to that listener port.
@@ -176,34 +176,34 @@ In the broker authorization rules for your authorization policy, use the followi
@@ -339,36 +339,36 @@ In the Broker authorization rules for your authorization policy, use the followi
339
339
340
340
```json
341
341
[
342
-
{
343
-
"brokerResources": [
344
-
{
345
-
"clientIds": [],
346
-
"method": "Connect",
347
-
"topics": []
348
-
},
349
-
{
350
-
"clientIds": [],
351
-
"method": "Publish",
352
-
"topics": [
353
-
"odd-numbered-orders"
354
-
]
355
-
},
356
-
{
357
-
"clientIds": [],
358
-
"method": "Subscribe",
359
-
"topics": [
360
-
"orders"
361
-
]
362
-
}
363
-
],
364
-
"principals": {
365
-
"attributes": [
366
-
{
367
-
"group": "authz-sat"
368
-
}
369
-
]
342
+
{
343
+
"brokerResources": [
344
+
{
345
+
"clientIds": [],
346
+
"method": "Connect",
347
+
"topics": []
348
+
},
349
+
{
350
+
"clientIds": [],
351
+
"method": "Publish",
352
+
"topics": [
353
+
"odd-numbered-orders"
354
+
]
355
+
},
356
+
{
357
+
"clientIds": [],
358
+
"method": "Subscribe",
359
+
"topics": [
360
+
"orders"
361
+
]
362
+
}
363
+
],
364
+
"principals": {
365
+
"attributes": [
366
+
{
367
+
"group": "authz-sat"
370
368
}
369
+
]
371
370
}
371
+
}
372
372
]
373
373
```
374
374
@@ -453,7 +453,7 @@ metadata:
453
453
namespace: azure-iot-operations
454
454
spec:
455
455
authorizationPolicies:
456
-
enableCache: false
456
+
cache: Enabled
457
457
rules:
458
458
- principals:
459
459
attributes:
@@ -472,11 +472,11 @@ spec:
472
472
473
473
To learn more with an example, see [Set up Authorization Policy with Dapr Client](../create-edge-apps/howto-develop-dapr-apps.md).
474
474
475
-
## Distributed state store
475
+
## State store
476
476
477
-
MQTT broker provides a distributed state store (DSS) that clients can use to store state. The DSS can also be configured to be highly available.
477
+
MQTT broker provides a [state store](../create-edge-apps/concept-about-state-store-protocol.md) that clients can use to store state. The state store can also be configured to be highly available.
478
478
479
-
To set up authorization for clients that use the DSS, provide the following permissions:
479
+
To set up authorization for clients that use the state store, provide the following permissions:
480
480
481
481
- Permission to publish to the system key value store `$services/statestore/_any_/command/invoke/request` topic
482
482
- Permission to subscribe to the response-topic (set during initial publish as a parameter) `<response_topic>/#`
0 commit comments