feat: JSON schema for Access Evaluation Request/Response #186
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Creating the json-schema 2020-12 schema for the
access evaluation requestandaccess evaluation responsefrom the schema define at Authzen - Authorization API 1.1 - draft 01Related issue
Additional note
We should consider some kind of testing to ensure that schema are compliant, as of today I'm manually validating via https://www.jsonschemavalidator.net/ and some basic example
a. ensure minimum schema
b. ensure the additional properties are allowed when allowed
The field $id should be replace with a more permanent id (eg: IANA registration ?)
We can reuse the schema to create an valid OAS 3.1 specs
We should provide guidance to people to generate "language specifics model" from json-schema or provide "authzen" own model via known platform (eg: maven)