Skip to content

Commit e7846b3

Browse files
committed
Editorial changes
1 parent 6ff54b7 commit e7846b3

4 files changed

Lines changed: 35 additions & 67 deletions

File tree

Lines changed: 33 additions & 64 deletions
Original file line numberDiff line numberDiff line change
@@ -1,98 +1,67 @@
11
---
2-
# Required metadata
3-
# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
4-
# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
5-
6-
title: 'AADSTS50017: Validation of Given Certificate for Certificate-Based Authentication Failed '
7-
description: 'AADSTS50017: Validation of Given Certificate for Certificate-Based Authentication Failed '
8-
author: Laks1 # GitHub alias
9-
ms.author: laks # Microsoft alias
2+
title: Error AADSTS50017 - Validation of Given Certificate for Certificate-Based Authentication Failed
3+
description: Provides solutions to the Microsoft Entra authentication AADSTS50017 error that occurs when you access an application or resource with certificate-based authentication (CBA).
4+
ms.reviewer: laks, joaos, willfid, v-weizhu
105
ms.service: entra-id
11-
ms.topic: troubleshooting-problem-resolution
12-
ms.date: 02/10/2025
13-
ms.subservice: authentication
6+
ms.date: 02/18/2025
7+
ms.custom: sap:Issues Signing In to Applications
148
---
15-
# Error AADSTS50017 - Validation of Given Certificate for Certificate-Based Authentication Failed
9+
# Error AADSTS50017 - Validation of given certificate for certificate-based authentication failed
1610

17-
This article discusses scenarios where the AADSTS50017 error occurs when a user accesses an application or resource with certificate-based authentication (CBA).
11+
This article provides solutions to the Microsoft Entra authentication AADSTS50017 error that occurs when you access an application or resource with certificate-based authentication (CBA).
1812

1913
## Symptoms
2014

21-
When a user tries to access an application or resource with Certificate-Based authentication ( CBA) the sign-in process fails, and the following error message is displayed:
15+
When you try to access an application or resource with CBA, the sign-in process fails and the following error message is displayed:
2216

2317
> AADSTS50017: Validation of given certificate for certificate based authentication failed.
2418
25-
## Scenario 1: Certificate chain failures due to missing CA Certificates in store or validation failures with SKI and AKI Values
19+
## Cause 1: Certificate chain failures or validation failures
2620

27-
## Solution :
21+
The AADSTS50017 error might occur because of the following problems:
2822

29-
1. Check if issuing certificate was correctly uploaded to the trusted certificates list. A certificate chain consists of multiple certificates linked together. The end-user’s certificate can be issued by a root CA, or by a non-root CA (a.k.a. intermediate CA).
23+
- Certificate chain failures due to missing certificate authority (CA) certificates in store.
24+
- Validation failures with Subject Key Identifier (SKI) and Authority Key Identifier (AKI) values.
3025

31-
2. If you have a non-root Issuing CA (intermediate CA), both intermediate and root CA certificates must be uploaded to the Entra ID CA trusted store.
26+
In Public Key Infrastructure (PKI), the certificate chain validation process ensures the integrity and authenticity of the certificate chain. The SKI and AKI play crucial roles in this process. The SKI provides a unique identifier for the public key held by the certificate. The AKI is used to identify the CA that issues the certificate.
3227

33-
3. In Public Key Infrastructure (PKI), the certificate chain validation process ensures the integrity and authenticity of the certificate chain. Below two key identifiers play a crucial role:
28+
To resolve this issue, follow these steps:
3429

35-
**Subject Key Identifier (SKI):** The **SKI** provides a unique identifier for the public key held by the certificate.
36-
**Authority Key Identifier (AKI):** The **AKI** is used to identify the certificate authority (CA) that issued the certificate.
30+
1. Check if issuing certificate is correctly uploaded to the trusted certificate list.
3731

38-
**1.1)** Check the SKI of the users certificate and confirm if the AKI matches any of the intermediate or root CAs it was uploaded to the trusted store.
32+
A certificate chain consists of multiple certificates linked together. The end-user's certificate can be issued by a root CA or a non-root CA (intermediate CA). If you have a non-root issuing CA (intermediate CA), both intermediate and root CA certificates must be uploaded to the Microsoft Entra CA trusted store.
3933

40-
It’s possible to check that information by navigating through the details of the user’s certificate and uploaded issuing CAs, as shown on the next pictures:
34+
2. Check the SKI value of your certificate and confirm if the AKI value matches any intermediate or root CA certificate that's uploaded to the trusted store.
4135

42-
![Screenshot of Certificate chain.](media/error-code-aadsts50017-certificate-based-authentication-failed/pic4.png)
36+
If there is no match, your certificate or the missing CA certificate should be changed accordingly. To do this, [configure certificate authorities by using the Microsoft Entra admin center](/entra/identity/authentication/how-to-certificate-based-authentication#configure-certificate-authorities-by-using-the-microsoft-entra-admin-center).
4337

38+
To get the SKI and AKI values, check the details of your certificate and uploaded issuing CA certificates.
4439

45-
1. **Root CA Certificate:**
46-
- Has its own SKI.
47-
- Issues the Intermediate certificates (when applicable).
48-
- The Root Certificate will not contain the Authority Key Identifier (AKI) field
40+
:::image type="content" source="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-chain.png" alt-text="Screenshot that shows a certificate chain." lightbox="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-chain.png":::
4941

50-
2. **Issuing or intermediate CA Certificate (when applicable):**
51-
- AKI points to the Root CA’s SKI.
52-
- Has its own SKI that will match the AKI on the user’s certificate.
53-
- Issues the user’s Certificate.
54-
- Multiple intermediate CAs can exist.
55-
- Issues the Intermediate certificates (when applicable).
42+
|Certificate type|Characteristic|
43+
|---|---|
44+
|Root CA certificate|It has its own SKI. It can issue the intermediate certificates when applicable. It doesn't contain the AKI field.|
45+
|Issuing or intermediate CA certificate (when applicable)|Its AKI points to the Root CA certificate's SKI. It has its own SKI that matches the AKI on a user certificate. It can issue user certificates, and issue intermediate certificates when applicable. Multiple intermediate CA certificates can exist.|
46+
|End-Entity (User or Client) certificate|It has its own SKI. Its AKI points to the issuing CA certificate's SKI.|
5647

57-
3. **End-Entity (User or Client) Certificate:**
58-
- Has its own SKI
59-
- AKI points to the Issuing CA’s SKI.
48+
## Cause 2: Invalid certificates
6049

61-
**1.2)** If there is no match, the missing CA certificates or the user’s certificate should be changed accordingly. Details under [Configure Certification Authorities using the Microsoft Entra Admin Center ](/entra/identity/authentication/how-to-certificate-based-authentication#configure-certification-authorities-using-the-microsoft-entra-admin-center).
50+
If any certificates in the certificate chain are missing valid extension identifiers, such as certificate policy extensions, the AADSTS50017 error might occur.
6251

52+
To resolve this error, validate the certificate policy extensions for all certificates within the certificate chain, including user certificates, intermediate CA certificates, and the root CA certificate. Ensure that the certificate policy extension and its Object Identifiers (OIDs) are consistent and valid across the entire chain.
6353

64-
## Scenario 2: Invalid CAs Where the Issuer Does Not Carry Valid Extension Identifiers.
54+
To verify the policy OIDs for consistency and validity, retrieve the relevant certificates in chain and validate them as shown below:
6555

66-
The AADSTS50017 error may also occur if any certificates in the chain are missing valid extension identifiers, such as certificate policy extensions.
56+
:::image type="content" source="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-policies.png" alt-text="Screenshot that shows certificate policies." lightbox="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-policies.png":::
6757

68-
## Solution :
6958

70-
2.1) Validate the Certificate Policies extensions for all certificates within the certificate chain, including user certificates, intermediate Certification Authority (CA) certificates, and the root CA certificate. Ensure that the Certificate Policies extension and its Object Identifiers (OIDs) are consistent and valid across the entire chain.
59+
If any certificates are missing certificate policy extensions, reissue the CA certificate or end user certificate with the appropriate certificate policy extensions embedded.
7160

72-
73-
74-
You can verify the policy Object Identifiers (OIDs) for consistency and validity by retrieving the relevant certificates in chain and validating them as shown below:
75-
76-
77-
78-
79-
80-
81-
82-
83-
84-
85-
![Screenshot-certificate-policies.](media/error-code-aadsts50017-certificate-based-authentication-failed/final-image-to-upload.png)
86-
87-
If any of the certificates are missing Certificate Policies extensions, it is necessary to reissue the Certification Authority (CA) certificate or end user certificate with the appropriate Certificate Policies extensions embedded.  
88-
89-
For more details about [policy extension and other supported extensions](/windows/win32/seccertenroll/supported-extensions), please refer to the following article:
61+
For more information about policy extension and other supported extensions, see [Supported Extensions](/windows/win32/seccertenroll/supported-extensions).
9062

9163
## AADSTS error code reference
9264

9365
For a full list of authentication and authorization error codes, see [Microsoft Entra authentication and authorization error codes](/entra/identity-platform/reference-error-codes). To investigate individual errors, search at https://login.microsoftonline.com/error.
9466

95-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
96-
97-
```
98-
67+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/entra/entra-id/app-integration/media/error-code-aadsts50017-certificate-based-authentication-failed/pic4.png renamed to support/entra/entra-id/app-integration/media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-chain.png

File renamed without changes.

support/entra/entra-id/app-integration/media/error-code-aadsts50017-certificate-based-authentication-failed/final-image-to-upload.png renamed to support/entra/entra-id/app-integration/media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-policies.png

File renamed without changes.

support/entra/entra-id/toc.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,9 +77,8 @@
7777
href: app-integration/error-code-AADSTS50020-user-account-identity-provider-does-not-exist.md
7878
- name: Error AADSTS530004 - AcceptCompliantDevice setting isn't configured
7979
href: app-integration/error-code-aadsts530004-acceptcompliantdevice-setting-not-configured.md
80-
- name: Error AADSTS50017 - Validation of Given Certificate for Certificate-Based
81-
Authentication Failed
82-
href: ./app-integration/error-code-aadsts50017-certificate-based-authentication-failed.md
80+
- name: Error AADSTS50017 - Validation of given certificate for certificate-based authentication failed
81+
href: app-integration/error-code-aadsts50017-certificate-based-authentication-failed.md
8382
- name: Error AADSTS50057 - user account is disabled
8483
href: app-integration/error-code-aadsts50057-user-account-is-disabled.md
8584
- name: Error AADSTS500571 - guest user account is disabled

0 commit comments

Comments
 (0)