Get a user's info
get
/ec-auth-svc/rest/v2.0/userinfo
Retrieves details for the currently logged-in user in v2 format. Response includes the user's identity, all global rights, and the complete list of key/value attributes.
Request
There are no request parameters for this operation.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Root Schema : UserInfoDtoV2
Type:
objectUser information with rights and attributes
Show Source
-
emailAddress: string
(email)
Email address of the user.Example:
jane.doe@example.com -
firstName: string
First name of the user.Example:
Jane -
globalRights: array
globalRights
Unique Items Required:
trueGlobal rights assigned to the user. -
lastName: string
Last name of the user.Example:
Doe -
userAttributes: object
userAttributes
Key-value pair for user attribute
-
userId: string
User identifier.Example:
A1234567890B1234567890C12345678E
Nested Schema : globalRights
Type:
arrayUnique Items Required:
trueGlobal rights assigned to the user.
Show Source
-
Array of:
string
Global rights assigned to the user.Example:
["OrsSiteShipmentPost","UpdateRecipe"]
Example:
[
"OrsSiteShipmentPost",
"UpdateRecipe"
]Nested Schema : userAttributes
Type:
objectKey-value pair for user attribute
Show Source
-
key: string
The attribute key nameExample:
Locale -
value: string
The value of the attributeExample:
en-US
Example:
{
"key":"Locale",
"value":"en-US"
}Examples
400 Response
Bad request
Root Schema : AuthResponse
Type:
objectGeneric API response wrapper containing result, error data, response version and status.
Show Source
-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
Result data of the API response; actual type depends on the API
-
status: string
(none)
Indicates request success ("success") or failure ("failure").Example:
success -
version: integer
(int32)
Version of the response schema.Example:
1
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: string
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.Example:
User role is missing required permission REPORTING_VIEW. Field: userId -
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectResult data of the API response; actual type depends on the API
Example:
oracle.doceng.json.BetterJsonNull@3565a0f5