Request based schema extensions #162
Unanswered
wesobi
asked this question in
Package Questions
Replies: 1 comment
-
Hi @q-uint, would a feature like this make sense? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Wanted to discuss whether or not request based schema extensions is something that you'd be interested in seeing into the package.
We're currently running this package as a SCIM server, processing requests for multiple customers (ranging from dozens with frequent/constant use to hundreds with sporadic use).
We're looking into allowing these customers to set their own custom attributes in our product and being able to provide these through SCIM. We'd store the structure of these attributes (value, type, ...) somewhere so we can parse the structure and create a schema we want to provide as an extension.
An example would be:
Customer A wants to store "seat location" as a custom attribute
When we get a request on the SCIM server for customer A, we want to include an "customSchema" extension that is created at runtime, having the "seat location" string as attribute. This extension should not outlive the request (so should only be for customer A's request)
Customer B wants to store "performance review score" as a custom attribute
When we get a request on the SCIM server for customer B, we want to include an "customSchema" extension that is created at runtime, having the "performance review score" string as attribute. This extension should not outlive the request (so should only be for customer B's request)
there are ways to deal with this on a different level (so not the package, but f.e. different infrastructure), thought that would not be feasible.
We can not store these as regular extensions in the current package setup as these would be different on each request (since the server deals with requests from multiple customers), so being able to "flexibly" add an extension on a request basis would be a solution to this.
I might be able to do this with a bit of tinkering in the resourcehandler, but that does not seem like a good location as we're already past any parsing and validating at that point.
Before doing more research on this (like working out a PoC, though I've already got some ideas on how to tackle it) specifically, i'd like to ask whether there is any interest at all in the feature. Else it might be a waste of time 😅
Beta Was this translation helpful? Give feedback.
All reactions