Get Account Sensitive Attributes
GET/api/v1/auth/accounts/:username/sensitive-attributes
Read an account's SENSITIVE attribute blob from the separate keyed store.
The account must exist first (404 otherwise), so a sensitive read cannot be used to probe for accounts that are not there. Soft-deleted accounts answer the same way.
Request
Responses
- 200
- 401
- 403
- 422
- default
Successful Response
No valid session: the credentials are missing, invalid or expired, or the account behind them is disabled or blocked
Refused: the session lacks the action this route checks, or its account must replace an issued password first. A SCIM route answers a refused action in the RFC 7644 error envelope
Validation Error
Problem details (RFC 9457)