---
title: Identity provider attributes
description: Map user attributes from an external identity provider to PingOne user attributes using SAML and JSON notation.
component: pingone
page_id: pingone:integrations:p1_idp_attributes
canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_idp_attributes.html
revdate: April 24, 2025
---

# Identity provider attributes

You can map user attributes from an external identity provider (IdP) *(tooltip: \<div class="paragraph">
\<p>A service that manages identity information and provides authentication services to relying clients or SPs within a federated or distributed network.\</p>
\</div>)* to PingOne user attributes using the appropriate notation for SAML and JSON.

When mapping user attributes, use the `providerAttributes` prefix rather than `samlAssertion` as follows:

```
providerAttributes.<IdP attribute name>
```

For example, mapping the email attribute from Facebook to PingOne would look like this:

```
providerAttributes.email
```

|   |                                                                                                                                                                                                                                                                                                               |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | For external IdPs that pass attributes in JSON structure (all external providers except SAML), the syntax for mapping attributes that use JSON dot notation, such as `name.family`, must use square brackets and single quotes around the attribute name as follows:```
providerAttributes['name.family']
``` |