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/logic-apps/logic-apps-securing-a-logic-app.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: klam, logicappspm
7
7
ms.topic: conceptual
8
-
ms.date: 02/04/2020
8
+
ms.date: 02/20/2020
9
9
---
10
10
11
11
# Secure access and data in Azure Logic Apps
@@ -734,39 +734,39 @@ When you use [secured parameters](#secure-action-parameters) to handle and prote
734
734
735
735
### Enable Azure AD OAuth authentication on Request triggers
736
736
737
-
If your logic app uses the Request trigger, you can use [Azure Active Directory OAuth](../active-directory/develop/about-microsoft-identity-platform.md) authentication for authorizing inbound calls to your logic app. Before you enable this authentication, review these considerations:
737
+
When your logic app starts with the Request trigger, you can use [Azure Active Directory (AD) OAuth](../active-directory/develop/about-microsoft-identity-platform.md) authentication for authorizing inbound calls to your logic app. Before you enable this authentication, review these considerations:
738
738
739
-
* Your logic app can have up to five authorization policies. Each authorization policy can have up to 10 claims.
739
+
* Your logic app can have up to five authorization policies. Each authorization policy can have up to 10 [claims](../active-directory/develop/developer-glossary.md#claim).
740
740
741
-
* An authorization policy must include at least the **Issuer**[claim](../active-directory/develop/developer-glossary.md#claim) whose value starts with the Azure Active Directory issuer ID, `https://sts.windows.net/`.
741
+
* An authorization policy must include at least the **Issuer** claim, which has a value that starts with `https://sts.windows.net/` as the Azure Active Directory issuer ID.
742
742
743
743
* Your logic app can't use both Azure AD OAuth [Shared Access Signatures (SAS)](#sas) for authorization.
744
744
745
745
* Currently, open authentication tokens are supported only for workflow trigger requests.
746
746
747
747
* Only Bearer-type authorization schemes are supported for OAuth tokens.
748
748
749
-
Now, to set up this authentication, follow these steps to add one or more authorization policies to your logic app.
749
+
To set up this authentication, follow these steps to add one or more authorization policies to your logic app.
750
750
751
751
1. In the [Azure portal](https://portal.microsoft.com), find and open your logic app in the Logic App Designer.
752
752
753
753
1. On the logic app menu, under **Settings**, select **Authorization**. After the Authorization pane opens, select **Add policy**.
1. Provide information about the authorization policy by specifying the claim types and values that your logic app requires from inbound requests:
757
+
1. Provide information about the authorization policy by specifying the [claim types](../active-directory/develop/developer-glossary.md#claim) and values that your logic app expects in the authentication tokens presented by inbound calls to the Request trigger:
758
758
759
759

760
760
761
761
| Property | Required | Description |
762
762
|----------|----------|-------------|
763
763
|**Policy name**| Yes | The name that you want to use for the authorization policy |
764
-
|**Claims**| Yes | The list of [claim](../active-directory/develop/developer-glossary.md#claim) types and values that incoming calls must use in the authentication tokens that they present to your logic app. This list requires at least one **Issuer**-type claim, which has a value that starts with the Azure AD issuer ID, `https://sts.windows.net/`. <p><p>Standard claims have these types: <p><p>- **Issuer** <br>- **Audience** <br>- **Subject** <br>- **JWT ID** <p><p>For more information about these claim types, see [Claims in Azure AD security tokens](../active-directory/azuread-dev/v1-authentication-scenarios.md#claims-in-azure-ad-security-tokens). You can also specify your own claim type and value.|
764
+
|**Claims**| Yes | The claim types and values that your logic app accepts from inbound calls. Here are the available standard claim types: <p><p>- **Issuer** <br>- **Audience** <br>- **Subject** <br>- **JWT ID** <p><p>At the minimum, the **Claims** list must include the **Issuer** claim, which has a value that starts with the `https://sts.windows.net/` Azure AD issuer ID. For more information about these claim types, see [Claims in Azure AD security tokens](../active-directory/azuread-dev/v1-authentication-scenarios.md#claims-in-azure-ad-security-tokens). You can also specify your own claim type and value. |
765
765
|||
766
766
767
767
1. To add another claim, select from these options:
768
768
769
-
* To add another standard claim type, select the claim type, and specify the claim value.
769
+
* To add another standard claim type, select **Add standard claim**, select the claim type, and specify the claim value.
770
770
771
771
* To add your own claim, select **Add custom claim**, and specify the custom claim value.
0 commit comments