It is possible to locate and retrieve user information from the resource server through SSOfy.
This feature only works if the resource server provides User Endpoint.
A microservice architecture is an example of a use case in which SSOfy acts as a proxy between the resource server and other services.
Here is a sample curl for finding a user by id:
curl --request POST 'https://api.ssofy.com/v1/resources/users/find' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Api-Key: cf47d697-cc0b-4262-8329-78a0995e6fd0' \
--header 'Signature: eyJoYXNoIjoiZGQ2ZDY0MDI3MWFkOTQ1NzA5MTdjZDE1MjA1YjI0YzdkYjVkMjcwMjk1OGFiZTM3MGFhODgzYzlkZGRhNTcxMSIsInNhbHQiOiJjODlqelJoeCJ9'
--data-raw '{
"id": "1"
}'
{
"user": {
"id": "1",
"display_name": "Sample User",
"name": "Sample",
"picture": "https://i.pravatar.cc/48",
"profile": "https://example.com/profile",
"additional": {
"Gender": "male"
}
}
}
See also User Entity
id
for which the type is compatible with lookups on ids of "numeric" or "string" types.
SSOfy replies with a JSON payload containing the user information provided by the resource server.
Verifying request and response signatures is strongly advised for security reasons.