Skip to content

Commit 87e2d30

Browse files
authored
Merge pull request #250274 from omondiatieno/problem-signin
troubleshoot sign in problem - UI updates
2 parents 8f79414 + 641424d commit 87e2d30

File tree

1 file changed

+29
-89
lines changed

1 file changed

+29
-89
lines changed

articles/active-directory/manage-apps/application-sign-in-problem-application-error.md

Lines changed: 29 additions & 89 deletions
Original file line numberDiff line numberDiff line change
@@ -21,17 +21,13 @@ In this scenario, Azure Active Directory (Azure AD) signs the user in. But the a
2121

2222
There are several possible reasons why the app didn't accept the response from Azure AD. If there's an error message or code displayed, use the following resources to diagnose the error:
2323

24-
* [Azure AD Authentication and authorization error codes](../develop/reference-error-codes.md)
25-
26-
* [Troubleshooting consent prompt errors](application-sign-in-unexpected-user-consent-error.md)
27-
24+
- [Azure AD Authentication and authorization error codes](../develop/reference-error-codes.md)
25+
- [Troubleshooting consent prompt errors](application-sign-in-unexpected-user-consent-error.md)
2826

2927
If the error message doesn't clearly identify what's missing from the response, try the following:
3028

31-
- If the app is the Azure AD gallery, verify that you followed the steps in [How to debug SAML-based single sign-on to applications in Azure AD](./debug-saml-sso-issues.md).
32-
29+
- If the app is in the Azure AD gallery, verify that you followed the steps in [How to debug SAML-based single sign-on to applications in Azure AD](./debug-saml-sso-issues.md).
3330
- Use a tool like [Fiddler](https://www.telerik.com/fiddler) to capture the SAML request, response, and token.
34-
3531
- Send the SAML response to the app vendor and ask them what's missing.
3632

3733
[!INCLUDE [portal updates](../includes/portal-update.md)]
@@ -40,32 +36,19 @@ If the error message doesn't clearly identify what's missing from the response,
4036

4137
To add an attribute in the Azure AD configuration that will be sent in the Azure AD response, follow these steps:
4238

43-
1. Open the [**Azure portal**](https://portal.azure.com/) and sign in as a global administrator or co-admin.
44-
45-
2. At the top of the navigation pane on the left side, select **All services** to open the Azure AD extension.
46-
47-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
48-
49-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
50-
51-
5. Select **All Applications** to view a list of your apps.
52-
53-
> [!NOTE]
54-
> 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."
55-
56-
6. Select the application that you want to configure for single sign-on.
57-
58-
7. After the app loads, select **Single sign-on** in the navigation pane.
59-
60-
8. In the **User Attributes** section, select **View and edit all other user attributes**. Here you can change which attributes to send to the app in the SAML token when users sign in.
39+
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).
40+
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
41+
1. Enter the name of the existing application in the search box, and then select the application that you want to configure for single sign-on.
42+
1. After the app loads, select **Single sign-on** in the navigation pane.
43+
1. In the **User Attributes** section, select **View and edit all other user attributes**. Here you can change which attributes to send to the app in the SAML token when users sign in.
6144

6245
To add an attribute:
6346

6447
1. Select **Add attribute**. Enter the **Name**, and select the **Value** from the drop-down list.
6548

6649
1. Select **Save**. You'll see the new attribute in the table.
6750

68-
9. Save the configuration.
51+
1. Save the configuration.
6952

7053
The next time that the user signs in to the app, Azure AD will send the new attribute in the SAML response.
7154

@@ -79,24 +62,11 @@ If you're using [Azure AD automated user provisioning](../app-provisioning/user-
7962

8063
To change the User Identifier value, follow these steps:
8164

82-
1. Open the [**Azure portal**](https://portal.azure.com/) and sign in as a global administrator or co-admin.
83-
84-
2. Select **All services** at the top of the navigation pane on the left side to open the Azure AD extension.
85-
86-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
87-
88-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
89-
90-
5. Select **All Applications** to view a list of your apps.
91-
92-
> [!NOTE]
93-
> 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."
94-
95-
6. Select the app that you want to configure for SSO.
96-
97-
7. After the app loads, select **Single sign-on** in the navigation pane.
98-
99-
8. Under **User attributes**, select the unique identifier for the user from the **User Identifier** drop-down list.
65+
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).
66+
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
67+
1. Select the app that you want to configure for SSO.
68+
1. After the app loads, select **Single sign-on** in the navigation pane.
69+
1. Under **User attributes**, select the unique identifier for the user from the **User Identifier** drop-down list.
10070

10171
### Change the NameID format
10272

@@ -108,26 +78,12 @@ Azure AD selects the format for the **NameID** attribute (User Identifier) based
10878

10979
To change which parts of the SAML token are digitally signed by Azure AD, follow these steps:
11080

111-
1. Sign in to the [Azure portal](https://portal.azure.com/) and sign in as a global administrator or co-admin.
112-
113-
2. Select **All services** at the top of the navigation pane on the left side to open the Azure AD extension.
114-
115-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
116-
117-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
118-
119-
5. Select **All Applications** to view a list of your apps.
120-
121-
> [!NOTE]
122-
> If you don't see the application that you want, use the **Filter** control at the top of the **All Applications List**. Set the **Show** option to "All Applications."
123-
124-
6. Select the application that you want to configure for single sign-on.
125-
126-
7. After the application loads, select **Single sign-on** in the navigation pane.
127-
128-
8. Under **SAML Signing Certificate**, select **Show advanced certificate signing settings**.
129-
130-
9. Select the **Signing Option** that the app expects from among these options:
81+
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).
82+
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
83+
1. Select the application that you want to configure for single sign-on.
84+
1. After the application loads, select **Single sign-on** in the navigation pane.
85+
1. Under **SAML Signing Certificate**, select **Show advanced certificate signing settings**.
86+
1. Select the **Signing Option** that the app expects from among these options:
13187

13288
- **Sign SAML response**
13389
- **Sign SAML response and assertion**
@@ -141,33 +97,17 @@ By default, Azure AD signs the SAML token by using the most-secure algorithm. We
14197

14298
To change the signing algorithm, follow these steps:
14399

144-
1. Sign in to the [Azure portal](https://portal.azure.com/) and sign in as a global administrator or co-admin.
145-
146-
2. Select **All services** at the top of the navigation pane on the left side to open the Azure AD extension.
147-
148-
3. Type **Azure Active Directory** in the filter search box, and then select **Azure Active Directory**.
149-
150-
4. Select **Enterprise Applications** in the Azure AD navigation pane.
151-
152-
5. Select **All Applications** to view a list of your applications.
153-
154-
> [!NOTE]
155-
> If you don't see the application that you want, use the **Filter** control at the top of the **All Applications List**. Set the **Show** option to "All Applications."
156-
157-
6. Select the app that you want to configure for single sign-on.
158-
159-
7. After the app loads, select **Single sign-on** from the navigation pane on the left side of the app.
160-
161-
8. Under **SAML Signing Certificate**, select **Show advanced certificate signing settings**.
162-
163-
9. Select **SHA-1** as the **Signing Algorithm**.
100+
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).
101+
1. Browse to **Identity** > **Applications** > **Enterprise applications** > **All applications**.
102+
1. Select the app that you want to configure for single sign-on.
103+
1. After the app loads, select **Single sign-on** from the navigation pane on the left side of the app.
104+
1. Under **SAML Signing Certificate**, select **Show advanced certificate signing settings**.
105+
1. Select **SHA-1** as the **Signing Algorithm**.
164106

165107
The next time that the user signs in to the app, Azure AD will sign the SAML token by using the SHA-1 algorithm.
166108

167109
## Next steps
168110

169-
* [How to debug SAML-based single sign-on to applications in Azure AD](./debug-saml-sso-issues.md).
170-
171-
* [Azure AD Authentication and authorization error codes](../develop/reference-error-codes.md)
172-
173-
* [Troubleshooting consent prompt errors](application-sign-in-unexpected-user-consent-error.md)
111+
- [How to debug SAML-based single sign-on to applications in Azure AD](./debug-saml-sso-issues.md)
112+
- [Azure AD Authentication and authorization error codes](../develop/reference-error-codes.md)
113+
- [Troubleshooting consent prompt errors](application-sign-in-unexpected-user-consent-error.md)

0 commit comments

Comments
 (0)