Verify user access using verification request ID
GET/groups-srv/verifications/:verificationId
This API call verifies if a user (sub) meets the access requirements defined in a stored verification request. The verification request must exist and the sub query parameter is required.
Purpose:
- Verify user access using a pre-configured verification request
- Reuse access control rules defined in verification requests
- Centralized access verification using stored rules
Parameters:
verificationId(path, required): The unique ID of the stored verification requestsub(query, required): The user ID to verify access for
Validation Rules:
verificationId: Required, must match pattern^[a-zA-Z0-9_-]+$, verification request must existsub: Required (query parameter), must be a valid user ID (UUID format), user must exist
Authentication Requirements:
- This endpoint requires authentication via Bearer token
- For anonymous tokens, the
cidaas:users_readscope is required - For authenticated non-admin users:
subquery parameter must match the token'ssub - Admin users can verify access for any user
Business Rules:
- The stored request's filters, matchCondition, and hints are applied to check user access
- Same verification logic as POST
/groups-srv/verificationsbut uses stored configuration - Response fields depend on the
hintsstored on the verification request - Useful for reusing access control rules across multiple verification calls
Request
Responses
- 200
- 400
- 401
- 404
OK
Bad Request - Missing sub parameter
Unauthorized
Not Found - Verification request not found