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/howto-saml-token-encryption.md
+29-7Lines changed: 29 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: app-mgmt
9
9
ms.workload: identity
10
10
ms.topic: conceptual
11
-
ms.date: 06/13/2023
11
+
ms.date: 06/15/2023
12
12
ms.author: jomondi
13
13
ms.reviewer: alamaral
14
14
ms.collection: M365-identity-device-management
@@ -22,8 +22,6 @@ ms.custom: enterprise-apps
22
22
23
23
SAML token encryption enables the use of encrypted SAML assertions with an application that supports it. When configured for an application, Azure AD will encrypt the SAML assertions it emits for that application using the public key obtained from a certificate stored in Azure AD. The application must use the matching private key to decrypt the token before it can be used as evidence of authentication for the signed in user.
24
24
25
-
This article provides instructions on how to configure token encryption for enterprise applications. It also provides instructions on how to configure SAML token encryption registered applications.
26
-
27
25
Encrypting the SAML assertions between Azure AD and the application provides additional assurance that the content of the token can't be intercepted, and personal or corporate data compromised.
28
26
29
27
Even without token encryption, Azure AD SAML tokens are never passed on the network in the clear. Azure AD requires token request/response exchanges to take place over encrypted HTTPS/TLS channels so that communications between the IDP, browser, and application take place over encrypted links. Consider the value of token encryption for your situation compared with the overhead of managing more certificates.
@@ -42,8 +40,8 @@ To configure enterprise application's SAML token encryption, follow these steps:
42
40
43
41
Create an asymmetric key pair to use for encryption. Or, if the application supplies a public key to use for encryption, follow the application's instructions to download the X.509 certificate.
44
42
45
-
The public key should be stored in an X.509 certificate file in .cer format.
46
-
43
+
The public key should be stored in an X.509 certificate file in .cer format. You can copy the contents of the certificate file to a text editor and save it as a .cer file. The certificate file should contain only the public key and not the private key.
44
+
47
45
If the application uses a key that you create for your instance, follow the instructions provided by your application for installing the private key that the application will use to decrypt tokens from your Azure AD tenant.
48
46
49
47
1. Add the certificate to the application configuration in Azure AD.
@@ -54,7 +52,9 @@ You can add the public cert to your application configuration within the Azure p
54
52
55
53
1. Go to the [Azure portal](https://portal.azure.com).
56
54
57
-
1. Go to the **Azure Active Directory > Enterprise applications** blade and then select the application that you wish to configure token encryption for.
55
+
1. Search for and select the **Azure Active Directory**.
56
+
57
+
1. Select **Enterprise applications** blade and then select the application that you wish to configure token encryption for.
58
58
59
59
1. On the application's page, select **Token encryption**.
60
60
@@ -170,7 +170,7 @@ To configure token encryption, follow these steps:
170
170
}
171
171
```
172
172
173
-
# [PowerShell](#tab/azure-powershell)
173
+
# [Azure AD PowerShell](#tab/azuread-powershell)
174
174
175
175
1. Use the latest Azure AD PowerShell module to connect to your tenant.
176
176
@@ -188,7 +188,29 @@ To configure token encryption, follow these steps:
1. Use the Microsoft Graph PowerShell module to connect to your tenant.
194
+
195
+
1. Set the token encryption settings using the **[Update-MgApplication](/powershell/module/microsoft.graph.applications/update-mgapplication?view=graph-powershell-1.0&preserve-view=true)** command.
1. Update the application's `keyCredentials` with an X.509 certificate for encryption. The following example shows a Microsoft Graph JSON payload with a collection of key credentials associated with the application.
0 commit comments