id
|
Identity URL, which is the same URL that was queried. |
asserted_user
|
Boolean value indicating whether the specified access token was issued for
this identity. |
user_id
|
User ID of the queried user. |
username
|
Username of the queried user. |
organization_id
|
ID of the queried user’s Salesforce org. |
nick_name
|
Experience Cloud nickname of the queried user. |
display_name
|
Display name (full name) of the queried user. |
email
|
Email address of the queried user. |
email_verified
|
Indicates whether the queried user’s email was verified by clicking a link in
the “Welcome to Salesforce” email.
The email_verified value
is set to true when users click a link in
the email they receive after the following:For example, a Salesforce admin creates the user Roberta Smith. Roberta
receives a “Welcome to Salesforce” email message with a link to verify her
account. After she clicks the link, the email_verified
value is set to true.
- They change their email address
- They change their password, or a Salesforce admin resets their
password
- They verify their identity when logging in from a new device or
browser
- A Salesforce admin creates them as a new user
|
first_name
|
First name of the queried user. |
last_name
|
Last name of the queried user. |
timezone
|
Time zone specified in the queried user’s settings |
photos
|
Map of URLs to the queried user’s profile pictures, specified as picture or thumbnail.
|
addr_street
|
Street specified in the address of the queried user’s settings. |
addr_city
|
City specified in the address of the queried user’s settings. |
addr_state
|
State specified in the address of the queried user’s settings. |
addr_country
|
Country specified in the address of the queried user’s settings. |
addr_zip
|
Zip or postal code specified in the address of the queried user’s
settings. |
mobile_phone
|
Mobile phone number specified in the queried user’s settings. |
mobile_phone_verified
|
Queried user confirmed that the mobile phone number is valid, |
status
|
Queried user’s current Chatter status.
created_date—xsd datetime value of the creation date of the
last post by the user, for example, 2010-05-08T05:17:51.000Z.body—Body of the post.
|
urls
|
Map containing various API endpoints that can be used with the queried user
enterprise (SOAP)metadata (SOAP)partner (SOAP)rest (REST)sobjects (REST)search (REST)query (REST)recent (REST)profilefeeds (Chatter)feed-items (Chatter)groups (Chatter)users (Chatter)custom_domain
|
active
|
Boolean specifying whether the queried user is active. |
user_type
|
Type of the queried user. |
language
|
Language of the queried user. |
locale
|
Locale of the queried user. |
utcOffset
|
Offset from UTC of the queried user’s time zone, in milliseconds. |
last_modified_date
|
xsd datetime format of the last
modification of the user, for example, 2010-06-28T20:54:09.000Z. |
is_app_installed
|
Value is true when the connected app is
installed in the user’s org, and the user’s access token was created using an
OAuth flow. If the connected app isn’t installed, the response doesn’t contain
this value. When parsing the response, check for the existence and value of this
property. |
mobile_policy
|
Specific values for managing a mobile connected app. These values are
available only when the connected app is installed in the current user’s org, the
app has a defined session timeout value, and the mobile PIN has a length value defined.
screen_lock—Length of time to
wait to lock the screen after inactivity.pin_length—Length of the
identification number required to gain access to the mobile app.
|
push_service_type
|
Set to apple if the connected app is
registered with Apple Push Notification Service (APNS) for iOS push notifications.
Set to androidGcm if it’s registered with
Google Cloud Messaging (GCM) for Android push notifications.
The response value
type is an array.
|
custom_permissions
|
When a request includes the custom_permissions scope parameter, the response
includes a map containing custom permissions in the org associated with the
connected app. If the connected app isn’t installed in the org or has no
associated custom permissions, the response doesn’t contain a custom_permissions map.
Here’s an example
request.
http://MyDomainName.my.salesforce.com/services/oauth2/authorize?response_type=token&client_
id=3MVG9lKcPoNINVBKV6EgVJiF.snSDwh6_2wSS7BrOhHGEJkC_&redirect_uri=http://www.example.org/qa/security/oauth
/useragent_flow_callback.jsp&scope=api%20id%20custom_permissions
Here’s
the JSON block in the identity URL
response.
"custom_permissions":
{
"Email.View":true,
"Email.Create":false,
"Email.Delete":false
}
|
