Limitations
The Security Verify Access SCIM application has some limitations.
General
- HTTP ETags support
Security Verify Access does not provide support for HTTP ETags. Resource responses will not contain the ETag HTTP header, and response bodies will not contain the meta attributes: created, lastModified, and version.
- Attribute case sensitivity
- Attribute names are always handled with case sensitivity. This rule also applies to attributes that are named in JSON bodies and in URL query string parameters.
- Resource filtering and sorting
- ISAM supports basic filtering operations using attribute operators. Filtering with logical operators or grouping operators is not supported. Sorting operations are not supported.
Unsupported endpoints
Security Verify Access does not provide the following endpoints defined is RFC 7643 and RFC 7644.
- Bulk operations and the /Bulk endpoint
- Security Verify Access does not support the bulk resource update endpoint.
- Search operations using the ./search endpoint
- Security Verify Access does not support query resources using HTTP POST functionality. This includes the endpoint /.search and any endpoint of the format <prefix>/.search.
Parent topic: User Self-Care with the SCIM API