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§
Structs§
- Multi
Value Attr - Scim
Entry - Scim
Entry Generic - 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
Entry GetQuery - SCIM Query Parameters used during the get of a single entry
- Scim
Entry Header - Scim
External Member - Scim
Mail - Scim
Meta - Scim
SshPub Key - Scim
SshPublic Key - Scim
Sync Group - Scim
Sync Group Builder - Scim
Sync Person - Scim
Sync Person Builder - Scim
Sync Request - Scim
Totp
Enums§
- Json
Value - Represents any valid JSON value.
- Scim
Attr - Scim
Oauth2 Claim MapJoin Char - Scim
Schema - Scim
Sync Retention Mode - Scim
Sync State - Scim
Value
Constants§
- SCIM_
ALGO - SCIM_
CONTENT_ TYPE - SCIM_
DIGITS - SCIM_
SCHEMA_ GROUP - SCIM_
SCHEMA_ PREIX - SCIM_
SCHEMA_ SYNC_ 1 - SCIM_
SCHEMA_ SYNC_ ACCOUNT - SCIM_
SCHEMA_ SYNC_ GROUP - SCIM_
SCHEMA_ SYNC_ PERSON - SCIM_
SCHEMA_ SYNC_ POSIXACCOUNT - SCIM_
SCHEMA_ SYNC_ POSIXGROUP - SCIM_
SCHEMA_ USER - SCIM_
SECRET - SCIM_
STEP