Closed quantranhong1999 closed 1 year ago
The endpoint could be GET /users/{username}/identities
API to get the default identity of a user
May not be needed? The LSC plugin would use the first identity that have mayDelete=true
as a pivot, create if none with maximum amount of fields populated with the LDAP data.
Misses sortOrder field, replyTo, bcc fields.
May not be needed? The LSC plugin would use the first identity that have mayDelete=true as a pivot, create if none with maximum amount of fields populated with the LDAP data.
Maybe. But I am not sure filtering on the LSC side could be done easily (long time no touch LSC), so I will let the GET default identity API for now.
With default=true
parameter,
the response should return json list (containing []
character)
Eg:
[
{
"id": "3739a34e-cd8c-3a42-bf28-578ba24da8ds",
"name": "Bob default identity",
"email": "bob@domain.tld",
...
"sortOrder": 3
}
]
Because the default
is just a query parameter, and the endpoint is not changed.
Why
API to list identities of a user
API to get the default identity of a user
Filtering the
mayDelete=true
with the highest prioritysortOrder
(smallest integer) Otherwise, return 404 not found.How
Use
IdentityRepository
list APIDoD