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/devices/troubleshoot-hybrid-join-windows-legacy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ If the device was not hybrid Azure AD joined, you can attempt to do hybrid Azure
85
85
86
86
- Autoworkplace.exe is unable to silently authenticate with Azure AD or AD FS. This could be caused by missing or misconfigured AD FS (for federated domains) or missing or misconfigured Azure AD Seamless Single Sign-On (for managed domains) or network issues.
87
87
88
-
- It could be that multi-factor authentication (MFA) is enabled/configured for the user and WIAORMUTLIAUTHN is not configured at the AD FS server.
88
+
- It could be that multi-factor authentication (MFA) is enabled/configured for the user and WIAORMULTIAUTHN is not configured at the AD FS server.
89
89
90
90
- Another possibility is that home realm discovery (HRD) page is waiting for user interaction, which prevents **autoworkplace.exe** from silently requesting a token.
summary: Azure Active Directory (Azure AD) is a multi-tenant, cloud-based identity and access management service.
5
+
brand: azure ## Used for color theming of icons and hero area
6
+
7
+
metadata:
8
+
title: Azure Active Directory Documentation - Tutorials, API Reference
9
+
description: Azure Active Directory (Azure AD) is Microsoft's multi-tenant, cloud-based directory, and identity management service that combines core directory services, application access management, and identity protection into a single solution.
10
+
author: mtillman
11
+
manager: daveba
12
+
ms.service: active-directory
13
+
ms.topic: hub-page
14
+
ms.date: 04/25/2019
15
+
ms.author: mtillman
16
+
ms.collection: M365-identity-device-management
17
+
18
+
highlightedContent:
19
+
items:
20
+
- title: What is Azure AD?
21
+
itemType: overview # controls the icon image and super-title text
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/application-proxy-configure-single-sign-on-with-ping-access.md
+36-4Lines changed: 36 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,9 +154,9 @@ To collect this information:
154
154
155
155
### Update GraphAPI to send custom fields (optional)
156
156
157
-
For a list of security tokens that Azure AD sends for authentication, see [Microsoft identity platform ID tokens](../develop/id-tokens.md). If you need a custom claim that sends other tokens, set the `acceptMappedClaims` application field to `True`. You can use Graph Explorer or the Azure AD portal's application manifest to make this change.
157
+
If you need a custom claim that sends other tokens within the access_token consumed by PingAccess, set the `acceptMappedClaims` application field to `True`. You can use Graph Explorer or the Azure AD portal's application manifest to make this change.
This example uses the [Azure Active Directory portal](https://aad.portal.azure.com/) to update the `acceptMappedClaims` field:
169
+
**This example uses the [Azure Active Directory portal](https://aad.portal.azure.com/) to update the `acceptMappedClaims` field:**
170
170
171
171
1. Sign in to the [Azure Active Directory portal](https://aad.portal.azure.com/) as an application administrator.
172
172
2. Select **Azure Active Directory** > **App registrations**. A list of applications appears.
@@ -175,7 +175,29 @@ This example uses the [Azure Active Directory portal](https://aad.portal.azure.c
175
175
5. Search for the `acceptMappedClaims` field, and change the value to `True`.
176
176
6. Select **Save**.
177
177
178
-
### Use a custom claim (optional)
178
+
179
+
### Use of optional claims (optional)
180
+
Optional claims allows you to add standard-but-not-included-by-default claims that every user and tenant has.
181
+
You can configure optional claims for your application by modifying the application manifest. For more info, see the [Understanding the Azure AD application manifest article](https://docs.microsoft.com/azure/active-directory/develop/reference-app-manifest/)
182
+
183
+
Example to include email address into the access_token that PingAccess will consume:
184
+
```
185
+
"optionalClaims": {
186
+
"idToken": [],
187
+
"accessToken": [
188
+
{
189
+
"name": "email",
190
+
"source": null,
191
+
"essential": false,
192
+
"additionalProperties": []
193
+
}
194
+
],
195
+
"saml2Token": []
196
+
},
197
+
```
198
+
199
+
### Use of claims mapping policy (optional)
200
+
[Claims Mapping Policy (preview)](https://docs.microsoft.com/azure/active-directory/develop/active-directory-claims-mapping#claims-mapping-policy-properties/) for attributes which do not exist in AzureAD. Claims mapping allows you to migrate old on-prem apps to the cloud by adding additional custom claims that are backed by your ADFS or user objects
179
201
180
202
To make your application use a custom claim and include additional fields, be sure you've also [created a custom claims mapping policy and assigned it to the application](../develop/active-directory-claims-mapping.md#claims-mapping-policy-assignment).
181
203
@@ -184,6 +206,16 @@ To make your application use a custom claim and include additional fields, be su
184
206
>
185
207
> You can do policy definition and assignment through PowerShell, Azure AD Graph Explorer, or Microsoft Graph. If you're doing them in PowerShell, you may need to first use `New-AzureADPolicy` and then assign it to the application with `Add-AzureADServicePrincipalPolicy`. For more information, see [Claims mapping policy assignment](../develop/active-directory-claims-mapping.md#claims-mapping-policy-assignment).
Add-AzureADServicePrincipalPolicy -Id "<<The object Id of the Enterprise Application you published in the previous step, which requires this claim>>" -RefObjectId $pol.Id
214
+
```
215
+
216
+
### Enable PingAccess to use custom claims (optional but required if you expect the application to consume additional claims)
217
+
When you will configure PingAccess in the following step, the Web Session you will create (Settings->Access->Web Sessions) must have **Request Profile** deselected and **Refresh User Attributes** set to **No**
218
+
187
219
## Download PingAccess and configure your application
188
220
189
221
Now that you've completed all the Azure Active Directory setup steps, you can move on to configuring PingAccess.
0 commit comments