Access Control layer type v0.9 #155
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Author: Gunnar Andersson <[email protected]>, MBition GmbH.
Access Control Layer
This defines an access control layer type that supports the addition of client ACLs and RBAC information applied to an interface described in the IFEX model.
Just like for previous layers, the README acts as a semi-formal specification and it describes the rules and definition of the layer type. A JSON schema is provided for strict definition and input validation of layers written in YAML.
A very rudimentary example is included with the core and applied layer file. Future work may extend with more comprehensive examples and test-cases.
Note that this is a v0.9 and some modifications can be expected.
The submission is provided under the main project license (LICENSE file in root of project).
The program was tested solely for our own use cases, which might differ from yours.
Provider Information