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/active-directory/authentication/how-to-nudge-authenticator-app.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
@@ -91,7 +91,7 @@ The following table lists **authenticationMethodsRegistrationCampaign** properti
91
91
92
92
| Name | Possible values | Description |
93
93
|------|-----------------|-------------|
94
-
| state |"enabled"<br>"disabled"<br>"default" | Allows you to enable or disable the feature.<br>Default value is used when the configuration hasn't been explicitly set and will use Azure AD default value for this setting. Currently maps to disabled.<br>Change states to either enabled or disabled as needed. |
94
+
| state |"enabled"<br>"disabled"<br>"default" | Allows you to enable or disable the feature.<br>Default value is used when the configuration hasn't been explicitly set and will use Azure AD default value for this setting. Currently maps to disabled.<br>Change states to either enabled or disabled as needed. |
95
95
| snoozeDurationInDays | Range: 0 – 14 | Defines after how many days the user will see the nudge again.<br>If the value is 0, the user is nudged during every MFA attempt.<br>Default: 1 day |
96
96
| includeTargets | N/A | Allows you to include different users and groups that you want the feature to target. |
97
97
| excludeTargets | N/A | Allows you to exclude different users and groups that you want omitted from the feature. If a user is in a group that is excluded and a group that is included, the user will be excluded from the feature.|
@@ -155,7 +155,7 @@ Here are a few sample JSONs you can use to get started!
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/blink-tutorial.md
+21-22Lines changed: 21 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,53 +72,52 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
72
72
73
73
1. On the **Basic SAML Configuration** section, enter the values for the following fields:
74
74
75
-
a. In the **Sign on URL** text box, type a URL using one of the following patterns:
76
-
75
+
1. In the **Sign on URL** text box, type a URL using one of the following patterns:
76
+
77
77
| Sign-on URL|
78
-
|------------|
78
+
|------------|
79
79
|`https://app.joinblink.com`|
80
80
|`https://<SUBDOMAIN>.joinblink.com`|
81
-
|
82
-
83
81
84
-
b. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
82
+
2. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
83
+
85
84
`https://api.joinblink.com/saml/o-<TENANTID>`
86
85
87
-
> [!NOTE]
88
-
> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [Blink Client support team](https://help.joinblink.com) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
86
+
> [!NOTE]
87
+
> These values are not real. Update these values with the actual Sign on URL and Identifier. Contact [Blink Client support team](https://help.joinblink.com) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
89
88
90
89
1. Blink Meetings application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes. Click **Edit** icon to open User Attributes dialog.
91
90
92
-
91
+
93
92
94
93
1. In addition to above, Blink Meetings application expects few more attributes to be passed back in SAML response. In the User Claims section on the User Attributes dialog, perform the following steps to add SAML token attribute as shown in the below table:
95
94
96
-
| Name | Source Attribute|
97
-
| ---------------| --------- |
98
-
| first_name | user.givenname |
99
-
| second_name | user.surname |
100
-
| email | user.mail |
95
+
| Name | Source Attribute|
96
+
| ---------------| --------- |
97
+
| first_name | user.givenname |
98
+
| second_name | user.surname |
99
+
| email | user.mail |
101
100
|||
102
101
103
-
a. Click **Add new claim** to open the **Manage user claims** dialog.
102
+
1. Click **Add new claim** to open the **Manage user claims** dialog.
104
103
105
-
b. In the **Name** textbox, type the attribute name shown for that row.
104
+
1. In the **Name** textbox, type the attribute name shown for that row.
106
105
107
-
c. Leave the **Namespace** blank.
106
+
1. Leave the **Namespace** blank.
108
107
109
-
d. Select Source as **Attribute**.
108
+
1. Select Source as **Attribute**.
110
109
111
-
e. From the **Source attribute** list, type the attribute value shown for that row.
110
+
1. From the **Source attribute** list, type the attribute value shown for that row.
112
111
113
-
f. Click **Save**.
112
+
1. Click **Save**.
114
113
115
114
1. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/egnyte-tutorial.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,21 +133,21 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
133
133
134
134
135
135
136
-
a. As **Single sign-on authentication**, select **SAML 2.0**.
137
-
138
-
b. As **Identity provider**, select **AzureAD**.
139
-
140
-
c. Paste **Login URL** copied from Azure portal into the **Identity provider login URL** textbox.
141
-
142
-
d. Paste **Azure AD Identifier** which you have copied from Azure portal into the **Identity provider entity ID** textbox.
143
-
144
-
e. Open your base-64 encoded certificate in notepad downloaded from Azure portal, copy the content of it into your clipboard, and then paste it to the **Identity provider certificate** textbox.
145
-
146
-
f. As **Default user mapping**, select **Email address**.
147
-
148
-
g. As **Use domain-specific issuer value**, select **disabled**.
149
-
150
-
h. Click **Save**.
136
+
1. As **Single sign-on authentication**, select **SAML 2.0**.
137
+
138
+
1. As **Identity provider**, select **AzureAD**.
139
+
140
+
1. Paste **Login URL** copied from Azure portal into the **Identity provider login URL** textbox.
141
+
142
+
1. Paste **Azure AD Identifier** which you have copied from Azure portal into the **Identity provider entity ID** textbox.
143
+
144
+
1. Open your base-64 encoded certificate in notepad downloaded from Azure portal, copy the content of it into your clipboard, and then paste it to the **Identity provider certificate** textbox.
145
+
146
+
1. As **Default user mapping**, select **Email address**.
147
+
148
+
1. As **Use domain-specific issuer value**, select **disabled**.
> These values are not real. Update these values with the actual Sign on URL, Identifier and Reply URL. Contact [Evidence.com Client support team](https://communities.taser.com/support/SupportContactUs?typ=LE) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
83
+
> These values are not real. Update these values with the actual Sign on URL, Identifier and Reply URL. Contact [Evidence.com Client support team](https://communities.taser.com/support/SupportContactUs?typ=LE) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
84
84
85
85
5. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/flatter-files-tutorial.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
@@ -118,12 +118,12 @@ To configure Azure AD single sign-on with Flatter Files, perform the following s
118
118
119
119
120
120
3. Click **Settings**, and then perform the following steps on the **Company** tab:
121
-
121
+
122
122
123
+
124
+
1. Select **Use SAML 2.0 for Authentication**.
123
125
124
-
a. Select **Use SAML 2.0 for Authentication**.
125
-
126
-
b. Click **Configure SAML**.
126
+
1. Click **Configure SAML**.
127
127
128
128
4. On the **SAML Configuration** dialog, perform the following steps:
> `<FORTIWEB_NAME>` is a name identifier that will be used later when supplying configuration to FortiWeb.
89
88
> Contact [FortiWeb Web Application Firewall support team](mailto:[email protected]) to get the real URL values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
90
89
91
90
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/freshdesk-tutorial.md
+28-28Lines changed: 28 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,10 +51,10 @@ Configure and test Azure AD SSO with FreshDesk using a test user called **B.Simo
51
51
To configure and test Azure AD SSO with FreshDesk, perform the following steps:
52
52
53
53
1.**[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
54
-
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
55
-
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
54
+
1.**[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with Britta Simon.
55
+
1.**[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable Britta Simon to use Azure AD single sign-on.
56
56
1.**[Configure FreshDesk SSO](#configure-freshdesk-sso)** - to configure the Single Sign-On settings on application side.
57
-
1. **[Create FreshDesk test user](#create-freshdesk-test-user)** - to have a counterpart of Britta Simon in FreshDesk that is linked to the Azure AD representation of user.
57
+
1.**[Create FreshDesk test user](#create-freshdesk-test-user)** - to have a counterpart of Britta Simon in FreshDesk that is linked to the Azure AD representation of user.
58
58
1.**[Test SSO](#test-sso)** - to verify whether the configuration works.
59
59
60
60
## Configure Azure AD SSO
@@ -67,29 +67,29 @@ To configure and test Azure AD SSO with FreshDesk, perform the following steps:
67
67
68
68
1. On the **Basic SAML Configuration** section, enter the values for the following fields:
69
69
70
-
a. In the **Sign-on URL** text box, type a URL using the following pattern:
70
+
1. In the **Sign-on URL** text box, type a URL using the following pattern:
71
71
`https://<tenant-name>.freshdesk.com` or any other value Freshdesk has suggested.
72
72
73
-
b. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
73
+
1. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
74
74
`https://<tenant-name>.freshdesk.com` or any other value Freshdesk has suggested.
75
75
76
-
c. In the **Reply URL** text box, type a URL using the following pattern:
76
+
1. In the **Reply URL** text box, type a URL using the following pattern:
77
77
`https://<tenant-name>.freshdesk.com/login/saml`
78
-
79
-
> [!NOTE]
80
-
> These values are not real. Update these values with the actual Sign on URL, Identifier and Reply URL. Contact [FreshDesk Client support team](https://freshdesk.com/helpdesk-software?utm_source=Google-AdWords&utm_medium=Search-IND-Brand&utm_campaign=Search-IND-Brand&utm_term=freshdesk&device=c&gclid=COSH2_LH7NICFVUDvAodBPgBZg) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
78
+
79
+
> [!NOTE]
80
+
> These values are not real. Update these values with the actual Sign on URL, Identifier and Reply URL. Contact [FreshDesk Client support team](https://freshdesk.com/helpdesk-software?utm_source=Google-AdWords&utm_medium=Search-IND-Brand&utm_campaign=Search-IND-Brand&utm_term=freshdesk&device=c&gclid=COSH2_LH7NICFVUDvAodBPgBZg) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
81
81
82
82
1. FreshDesk application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes, whereas **Unique User Identifier** is mapped with **user.userprincipalname** but FreshDesk expects this claim to be mapped with **user.mail**, so you need to edit the attribute mapping by clicking on Edit icon and change the attribute mapping.
83
83
84
-
84
+
85
85
86
86
1. On the **Set-up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, click **Download** to download the **Certificate (Base64)** from the given options as per your requirement and save it on your computer.
0 commit comments