Expand description
These represent Kanidm’s view of SCIM resources that a client will serialise for transmission, and the server will deserialise to process them. In reverse Kanidm will send responses that a client can then process and use.
A challenge of this is that it creates an asymmetry between the client and server as SCIM contains very few strong types. Without awareness of what the client or server intended it’s not possible to directly deserialise into a rust strong type on the receiver. To resolve this, this library divides the elements into multiple parts.
The scim_proto library, which is generic over all scim implementations.
The client module, which describes how a client should transmit entries, and how it should parse them when it receives them.
The server module, which describes how a server should transmit entries and how it should receive them.
Modules§
- These are types that a client will send to the server.
Structs§
- A generic ScimEntry. This retains attribute values in a generic state awaiting processing by schema aware transforms either by the server or the client.
- SCIM Query Parameters used during the get of a single entry
Enums§
- Represents any valid JSON value.