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/manage-apps/troubleshoot-password-based-sso.md
+21-31Lines changed: 21 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.service: active-directory
7
7
ms.subservice: app-mgmt
8
8
ms.workload: identity
9
9
ms.topic: troubleshooting
10
-
ms.date: 07/11/2017
10
+
ms.date: 09/07/2023
11
11
ms.author: jomondi
12
12
ms.reviewer: alamaral
13
13
ms.custom: enterprise-apps
@@ -89,18 +89,13 @@ In general, if automatic sign-in field capture doesn't work, try the manual opti
89
89
90
90
To configure password-based SSO by using automatic sign-in field capture, follow these steps:
91
91
92
-
1. Sign in to the [Azure portal](https://portal.azure.com/). Sign in as a global administrator or co-admin.
93
-
2. In the navigation pane on the left side, select **All services** to open the Azure AD extension.
94
-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
95
-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
96
-
5. Select **All Applications** to view a list of your apps.
97
-
> [!NOTE]
98
-
> If you don't see the app that you want, use the **Filter** control at the top of the **All Applications** list. Set the **Show** option to "All Applications."
99
-
6. Select the app that you want to configure for SSO.
100
-
7. After the app loads, select **Single sign-on** in the navigation pane on the left side.
101
-
8. Select **Password-based Sign-on** mode.
102
-
9. Enter the **Sign-on URL**, which is the URL of the page where users enter their user name and password to sign in. *Make sure that the sign-in fields are visible on the page for the URL that you provide*.
103
-
10. Select **Save**.
92
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
1. Select the app that you want to configure for SSO.
95
+
1. After the app loads, select **Single sign-on** in the navigation pane on the left side.
96
+
1. Select **Password-based Sign-on** mode.
97
+
1. Enter the **Sign-on URL**, which is the URL of the page where users enter their user name and password to sign in. *Make sure that the sign-in fields are visible on the page for the URL that you provide*.
98
+
1. Select **Save**.
104
99
The page is automatically scraped for the user name and password input boxes. You can now use Azure AD to securely transmit passwords to that app by using the My Apps browser extension.
105
100
106
101
### Manually capture sign-in fields for an app
@@ -109,22 +104,17 @@ To manually capture sign-in fields, you must have the My Apps browser extension
109
104
110
105
To configure password-based SSO for an app by using manual sign-in field capture, follow these steps:
111
106
112
-
1. Sign in to the [Azure portal](https://portal.azure.com/). Sign in as a global administrator or co-admin.
113
-
2. In the navigation pane on the left side, select **All services** to open the Azure AD extension.
114
-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
115
-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
116
-
5. Select **All Applications** to view a list of your apps.
117
-
> [!NOTE]
118
-
> If you don't see the app that you want, use the **Filter** control at the top of the **All Applications** list. Set the **Show** option to "All Applications."
119
-
6. Select the app that you want to configure for SSO.
120
-
7. After the app loads, select **Single sign-on** in the navigation pane on the left side.
121
-
8. Select **Password-based Sign-on** mode.
122
-
9. Enter the **Sign-on URL**, which is the page where users enter their user name and password to sign in. *Make sure that the sign-in fields are visible on the page for the URL that you provide*.
123
-
10. Select **Configure *<appname>* Password Single Sign-on Settings**.
124
-
11. Select **Manually detect sign-in fields**.
125
-
12. Select **Ok**.
126
-
13. Select **Save**.
127
-
14. Follow the instructions to use My Apps.
107
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
1. Select the app that you want to configure for SSO.
110
+
1. After the app loads, select **Single sign-on** in the navigation pane on the left side.
111
+
1. Select **Password-based Sign-on** mode.
112
+
1. Enter the **Sign-on URL**, which is the page where users enter their user name and password to sign in. *Make sure that the sign-in fields are visible on the page for the URL that you provide*.
113
+
1. Select **Configure *<appname>* Password Single Sign-on Settings**.
114
+
1. Select **Manually detect sign-in fields**.
115
+
1. Select **Ok**.
116
+
1. Select **Save**.
117
+
1. Follow the instructions to use My Apps.
128
118
129
119
## Troubleshoot problems
130
120
@@ -183,8 +173,8 @@ If you get an error message when you set up SSO and assign users, open a support
183
173
184
174
To see the details of any portal notification, follow these steps:
185
175
186
-
1. Select the **Notifications** icon (the bell) in the upper-right corner of the Azure portal.
187
-
2. Select any notification that shows an *Error* state. (They have a red "!".)
176
+
1. Select the **Notifications** icon (the bell) in the upper-right corner of the Microsoft Entra admin center.
177
+
2. Select any notification that shows an **Error** state. (They have a red "!".)
188
178
> [!NOTE]
189
179
> You can't select notifications that are in the *Successful* or *In Progress* state.
190
180
3. The **Notification Details** pane opens. Read the information to learn about the problem.
0 commit comments