Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic validation based upon resource/extension type definition. #13

Open
dgioulakis opened this issue Mar 5, 2016 · 0 comments
Open

Comments

@dgioulakis
Copy link
Contributor

dgioulakis commented Mar 5, 2016

Currently, Owin.Scim does not provide any validation business logic based upon resource or extension schema definitions. When you add a resource and/or extension, you must specify a concrete type of validator that implements IValidator<T>.

Can we create an abstract validator that takes a IScimTypeDefinition and adds rules according to the schema rules and canonical values?

                            default rule-set
-----------------------------------------------------------------------
required.true           |   notEmpty
canonicalValues         |   <validate using CanonicalValueComparer>
  1. Is it even worth the effort?
  2. This does not cover the entire specification validation. For instance, user.Locale must be a valid language tag as defined in RFC5646.
  3. Should we provide additional extensibility points that allow you to create an IRuleBuilder when defining your schema?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant