Skip to content

Serialize and validate according to ServiceProviderConfig #25

Open
@azmeuk

Description

@azmeuk
Contributor

Passing ServiceProviderConfig to the serialization and validation context would allow to check for additional things.

For example:

  • if changePassword is not supported by a server, then it could raise a ValidationError when used in a RESOURCE_REPLACEMENT_QUERY_CONTEXT for instance.
  • if etag is not supported, then response contexts should reject payloads containing etags.
  • if filter or sort are not supported, then they should not be passed when building SearchRequest objects.

Activity

changed the title [-]Serialize and validate according to `ServiceProviderConfiguration`[/-] [+]Serialize and validate according to `ServiceProviderConfig`[/+] on Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @azmeuk

        Issue actions

          Serialize and validate according to `ServiceProviderConfig` · Issue #25 · python-scim/scim2-models