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/active-directory-saas-access-panel-introduction.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,10 @@ To use internal company URLs while remote using the extension, do the following:
103
103
3. Install the extension, and sign in to it by selecting Sign in to get started.
104
104
4. You can now browse to the internal company URL even while remote.
105
105
106
+
> [!NOTE]
107
+
> You may also turn off automatic redirection to company URLs by selecting the settings gear on the main menu and selecting **off** for the Company internal URL redirection option.
108
+
109
+
106
110
## Mobile app support
107
111
108
112
The Azure Active Directory team publishes the My Apps mobile app. When you install the app, you can sign in to password-based SSO applications on iOS and Android devices.
Copy file name to clipboardExpand all lines: articles/active-directory/develop/active-directory-v2-protocols-implicit.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ The entire implicit sign-in flow looks something like this - each of the steps a
47
47
To initially sign the user into your app, you can send an [OpenID Connect](active-directory-v2-protocols-oidc.md) authorization request and get an `id_token` from the v2.0 endpoint:
48
48
49
49
> [!IMPORTANT]
50
-
> In order to succesfully request an ID token, the app registration in the [registration portal](https://apps.dev.microsoft.com) must have the **[Implicit grant](active-directory-v2-protocols-implicit.md)** enabled for the the Web client. If it is not enabled, an `unsupported_response` error will be returned: "The provided value for the input parameter 'response_type' is not allowed for this client. Expected value is 'code'"
50
+
> In order to succesfully request an ID token, the app registration in the [registration portal](https://apps.dev.microsoft.com) must have the **[Implicit grant](active-directory-v2-protocols-implicit.md)** enabled for the Web client. If it is not enabled, an `unsupported_response` error will be returned: "The provided value for the input parameter 'response_type' is not allowed for this client. Expected value is 'code'"
Copy file name to clipboardExpand all lines: articles/active-directory/develop/active-directory-v2-protocols-oidc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ When your web app needs to authenticate the user, it can direct the user to the
81
81
* The request must include the `nonce` parameter.
82
82
83
83
> [!IMPORTANT]
84
-
> In order to succesfully request an ID token, the app registration in the [registration portal](https://apps.dev.microsoft.com) must have the **[Implicit grant](active-directory-v2-protocols-implicit.md)** enabled for the the Web client. If it is not enabled, an `unsupported_response` error will be returned: "The provided value for the input parameter 'response_type' is not allowed for this client. Expected value is 'code'"
84
+
> In order to succesfully request an ID token, the app registration in the [registration portal](https://apps.dev.microsoft.com) must have the **[Implicit grant](active-directory-v2-protocols-implicit.md)** enabled for the Web client. If it is not enabled, an `unsupported_response` error will be returned: "The provided value for the input parameter 'response_type' is not allowed for this client. Expected value is 'code'"
Copy file name to clipboardExpand all lines: articles/active-directory/device-management-hybrid-azuread-joined-devices-setup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -266,7 +266,7 @@ The definition helps you to verify whether the values are present or if you need
266
266
267
267
### Issue objectSID of the computer account on-premises
268
268
269
-
**`http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid`** - This claim must contain the the **objectSid** value of the on-premises computer account. In AD FS, you can add an issuance transform rule that looks like this:
269
+
**`http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid`** - This claim must contain the **objectSid** value of the on-premises computer account. In AD FS, you can add an issuance transform rule that looks like this:
270
270
271
271
@RuleName = "Issue objectSID for domain-joined computers"
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/ciscocloudlock-tutorial.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ The objective of this section is to create a test user in the Azure portal calle
163
163
164
164
### Create a The Cloud Security Fabric test user
165
165
166
-
In this section, you create a user called Britta Simon in The Cloud Security Fabric. Work with [The Cloud Security Fabric support team](mailto:[email protected]) to add the users in the The Cloud Security Fabric platform. Users must be created and activated before you use single sign-on.
166
+
In this section, you create a user called Britta Simon in The Cloud Security Fabric. Work with [The Cloud Security Fabric support team](mailto:[email protected]) to add the users in The Cloud Security Fabric platform. Users must be created and activated before you use single sign-on.
167
167
168
168
### Assign the Azure AD test user
169
169
@@ -179,7 +179,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
179
179
180
180
2. In the applications list, select **The Cloud Security Fabric**.
181
181
182
-

182
+

183
183
184
184
3. In the menu on the left, click **Users and groups**.
185
185
@@ -199,7 +199,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
199
199
200
200
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
201
201
202
-
When you click the The Cloud Security Fabric tile in the Access Panel, you should get automatically signed-on to your The Cloud Security Fabric application.
202
+
When you click The Cloud Security Fabric tile in the Access Panel, you should get automatically signed-on to your The Cloud Security Fabric application.
203
203
For more information about the Access Panel, see [Introduction to the Access Panel](../active-directory-saas-access-panel-introduction.md).
Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/intralinks-tutorial.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,7 +235,7 @@ After that you can follow the below procedure to add another Intralinks applicat
235
235
236
236

237
237
238
-
8. Get the the SP Initiated SSO URL from [Intralinks team](https://www.intralinks.com/contact-1) for the other Intralinks application and enter it in **Configure Sign-on URL** as shown below.
238
+
8. Get the SP Initiated SSO URL from [Intralinks team](https://www.intralinks.com/contact-1) for the other Intralinks application and enter it in **Configure Sign-on URL** as shown below.
239
239
240
240

Copy file name to clipboardExpand all lines: articles/active-directory/saas-apps/jostle-tutorial.md
+34-34Lines changed: 34 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ To test the steps in this tutorial, you should follow these recommendations:
45
45
- If you don't have an Azure AD trial environment, you can get a one-month trial [here](https://azure.microsoft.com/pricing/free-trial/).
46
46
47
47
## Scenario description
48
-
In this tutorial, you test Azure AD single sign-on in a test environment.
48
+
In this tutorial, you test Azure AD single sign-on in a test environment.
49
49
The scenario outlined in this tutorial consists of two main building blocks:
50
50
51
51
1. Adding Jostle from the gallery
@@ -56,21 +56,21 @@ To configure the integration of Jostle into Azure AD, you need to add Jostle fro
56
56
57
57
**To add Jostle from the gallery, perform the following steps:**
58
58
59
-
1. In the **[Azure portal](https://portal.azure.com)**, on the left navigation panel, click **Azure Active Directory** icon.
59
+
1. In the **[Azure portal](https://portal.azure.com)**, on the left navigation panel, click **Azure Active Directory** icon.
60
60
61
61
![Active Directory][1]
62
62
63
63
2. Navigate to **Enterprise applications**. Then go to **All applications**.
64
64
65
65
![Applications][2]
66
-
67
-
3. To add new application, click **New application** button on the top of dialog.
68
66
69
-
![Applications][3]
67
+
3. Click **Add** at the top of the window.
70
68
71
-
4. In the search box, type **Jostle**.
69
+

72
70
73
-

71
+
4. In the search box under **Add an application** type **Jostle**.
72
+
73
+

74
74
75
75
5. In the results panel, select **Jostle**, and then click **Add** button to add the application.
76
76
@@ -102,35 +102,36 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
102
102
![Configure Single Sign-On][4]
103
103
104
104
2. On the **Single sign-on** dialog, select **Mode** as **SAML-based Sign-on** to enable single sign-on.
105
-
105
+
106
106

107
107
108
108
3. On the **Jostle Domain and URLs** section, perform the following steps:
109
109
110
-

110
+

111
+
112
+
a. In the **Sign-on URL** textbox, enter: `https://login-prod.jostle.us`
111
113
112
-
a. In the **Sign-on URL** textbox, type a URL using the following pattern: `https://<tanent name>.jostle.us/jostle-prod/`
114
+
b. In the **Identifier** textbox, enter: `https://jostle.us`
113
115
114
-
b. In the **Identifier** textbox, type a URL using the following pattern: `https://<tanent name>.jostle.us`
116
+
c. Check the box next to **Show advanced URL settings**
115
117
116
-
> [!NOTE]
117
-
> These values are not real. Update these values with the actual Sign-On URL and Identifier. Contact [Jostle support team](mailto:[email protected]) to get these values.
118
-
118
+
d. In the **Reply URL** textbox, enter: `https://login-prod.jostle.us/saml/SSO/alias/newjostle.us`
119
119
120
+
4. On the **User Attributes** section, for the **User Identifier** field, enter: `user.userprincipalname`
120
121
121
-
4. On the **SAML Signing Certificate** section, click **Metadata XML** and then save the metadata file on your computer.
122
+

122
123
123
-

124
+
5. Click **Save** at the top of the window.
124
125
125
-
5. Click **Save**button.
126
+
6. Go to **SAML Signing Certificate**and verify that it's set to **Active**. Then click **Metadata XML** to download the metadata file.
126
127
127
-

128
+

128
129
129
-
7. To configure single sign-on on Jostle side, you need to send the downloaded metadata XML to [Jostle support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
130
+
7. To configure single sign-on on Jostle's side, you need to send the downloaded metadata XML to [Jostle support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
130
131
131
132
> [!TIP]
132
133
> You can now read a concise version of these instructions inside the [Azure portal](https://portal.azure.com), while you are setting up the app! After adding this app from the **Active Directory > Enterprise Applications** section, simply click the **Single Sign-On** tab and access the embedded documentation through the **Configuration** section at the bottom. You can read more about the embedded documentation feature here: [Azure AD embedded documentation](https://go.microsoft.com/fwlink/?linkid=845985)
133
-
>
134
+
>
134
135
135
136
### Creating an Azure AD test user
136
137
The objective of this section is to create a test user in the Azure portal called Britta Simon.
@@ -141,19 +142,19 @@ The objective of this section is to create a test user in the Azure portal calle
141
142
142
143
1. In the **Azure portal**, on the left navigation pane, click **Azure Active Directory** icon.
143
144
144
-

145
+

145
146
146
147
2. To display the list of users, go to **Users and groups** and click **All users**.
147
-
148
-

148
+
149
+

149
150
150
151
3. To open the **User** dialog, click **Add** on the top of the dialog.
151
-
152
-

152
+
153
+

153
154
154
155
4. On the **User** dialog page, perform the following steps:
155
-
156
-

156
+
157
+

157
158
158
159
a. In the **Name** textbox, type **BrittaSimon**.
159
160
@@ -162,7 +163,7 @@ The objective of this section is to create a test user in the Azure portal calle
162
163
c. Select **Show Password** and write down the value of the **Password**.
163
164
164
165
d. Click **Create**.
165
-
166
+
166
167
### Creating a Jostle test user
167
168
168
169
In this section, you create a user called Britta Simon in Jostle. If you don't know how to add Britta Simon in Jostle, please contact with [Jostle support team](mailto:[email protected]) to add the test user and enable SSO.
@@ -174,21 +175,21 @@ In this section, you create a user called Britta Simon in Jostle. If you don't k
174
175
175
176
In this section, you enable Britta Simon to use Azure single sign-on by granting access to Jostle.
176
177
177
-
![Assign User][200]
178
+
![Assign User][200]
178
179
179
180
**To assign Britta Simon to Jostle, perform the following steps:**
180
181
181
182
1. In the Azure portal, open the applications view, and then navigate to the directory view and go to **Enterprise applications** then click **All applications**.
182
183
183
-
![Assign User][201]
184
+
![Assign User][201]
184
185
185
186
2. In the applications list, select **Jostle**.
186
187
187
-

188
+

188
189
189
190
3. In the menu on the left, click **Users and groups**.
190
191
191
-
![Assign User][202]
192
+
![Assign User][202]
192
193
193
194
4. Click **Add** button. Then select **Users and groups** on **Add Assignment** dialog.
194
195
@@ -199,7 +200,7 @@ In this section, you enable Britta Simon to use Azure single sign-on by granting
199
200
6. Click **Select** button on **Users and groups** dialog.
200
201
201
202
7. Click **Assign** button on **Add Assignment** dialog.
202
-
203
+
203
204
### Testing single sign-on
204
205
205
206
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
@@ -227,4 +228,3 @@ For more information about the Access Panel, see [Introduction to the Access Pan
0 commit comments