Skip to content

Commit 7d64f4a

Browse files
authored
Merge pull request #8181 from Laks1/docs-editor/error-code-aadsts50017-certifi-1739189007
AB#3831: Create article error-code-aadsts50017-certificate-based-authentication-failed
2 parents 4948acf + 5be9bbb commit 7d64f4a

File tree

4 files changed

+68
-0
lines changed

4 files changed

+68
-0
lines changed
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
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
5+
ms.service: entra-id
6+
ms.date: 02/25/2025
7+
ms.custom: sap:Issues Signing In to Applications
8+
---
9+
# Error AADSTS50017 - Validation of given certificate for certificate-based authentication failed
10+
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).
12+
13+
## Symptoms
14+
15+
When you try to access an application or resource with CBA, the sign-in process fails and the following error message is displayed:
16+
17+
> AADSTS50017: Validation of given certificate for certificate based authentication failed.
18+
19+
## Cause 1: Certificate chain failures or validation failures
20+
21+
The AADSTS50017 error might occur because of the following problems:
22+
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.
25+
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.
27+
28+
To resolve this issue, follow these steps:
29+
30+
1. Check if issuing certificate is correctly uploaded to the trusted certificate list.
31+
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.
33+
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.
35+
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).
37+
38+
To get the SKI and AKI values, check the details of your certificate and uploaded issuing CA certificates.
39+
40+
:::image type="content" source="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-chain-ski-aki-value.png" alt-text="Screenshot that shows a certificate chain." lightbox="media/error-code-aadsts50017-certificate-based-authentication-failed/certificate-chain-ski-aki-value.png":::
41+
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.|
47+
48+
## Cause 2: Invalid certificates
49+
50+
If any certificates in the certificate chain are missing valid extension identifiers, such as certificate policy extensions, the AADSTS50017 error might occur.
51+
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.
53+
54+
To verify the policy OIDs for consistency and validity, retrieve the relevant certificates in chain and validate them as follows:
55+
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":::
57+
58+
If any certificates are missing certificate policy extensions, reissue the CA certificate or end user certificate with the appropriate certificate policy extensions embedded.
59+
60+
For more information about policy extension and other supported extensions, see [Supported Extensions](/windows/win32/seccertenroll/supported-extensions).
61+
62+
## AADSTS error code reference
63+
64+
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.
65+
66+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Loading
Loading

support/entra/entra-id/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,8 @@
7979
href: app-integration/error-code-AADSTS50020-user-account-identity-provider-does-not-exist.md
8080
- name: Error AADSTS530004 - AcceptCompliantDevice setting isn't configured
8181
href: app-integration/error-code-aadsts530004-acceptcompliantdevice-setting-not-configured.md
82+
- name: Error AADSTS50017 - Validation of given certificate for certificate-based authentication failed
83+
href: app-integration/error-code-aadsts50017-certificate-based-authentication-failed.md
8284
- name: Error AADSTS50057 - user account is disabled
8385
href: app-integration/error-code-aadsts50057-user-account-is-disabled.md
8486
- name: AADSTS500011 - Resource Principal Not Found

0 commit comments

Comments
 (0)