scim2-models
scim2-models copied to clipboard
SCIM resources serialization and validation with Pydantic
[RFC9865](https://www.rfc-editor.org/rfc/rfc9865.html) details cursor-based pagination. scim2-models should probably support this.
https://github.com/python-scim/scim2-models/blob/00031eb0a4fa41c6f57631600021bf3019351976/scim2_models/base.py#L413 For server implementations clients often send fields not permitted or defined in the model This is unfortunate however for compatibility we need to allow but ignore fields we don't...
Currently the path management is tedious, specially in path_op.py. There are a lot of `split(":")` and `":" in path` and `split(".")` and `"."` in path to manage path urn prefixes,...
Currently resources must define a `schemas : list[str]` attribute and assign a list with the schema. This is not ideal, and there is no check performed on the schema attribute...
scim2-models should use a `SCIMConfig` object to define a few behaviors: - attribute case sensitivity #39 - accepting extra inputs #85 - custom Entra PATCH values https://github.com/python-scim/scim2-server/issues/13 - whether a...
Find a clever way to reuse the `Error` objects in the Python exceptions. This would improve the error management in `PatchOp`. Also it would be nice to provide additional context...
scim2-models should support path filters described in [RFC7644 §3.4.2.2](https://datatracker.ietf.org/doc/html/rfc7644#section-3.4.2.2) for search and patch requests. Related project: https://scim2-filter-parser.readthedocs.io/en/stable/
According to [RFC7643 §6](https://datatracker.ietf.org/doc/html/rfc7643#section-6), ResourceTypes can define required and optional extensions. This information should be used in the validation process. This raises challenge though, as for the moment there is...