Add a resource to the authorization section #131
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.
I'd like to submit a blog post for your consideration, it is about the evolution of fine-grained authorization and how the age of SaaS and cloud have impacted the requirements for application access control.
This links is special because it brings into light how the shift from monoliths to microservice based architecture have changed the requirements from authorization services. What once could be tackled by a library or central SaaS offering today requires a distributed systems architecture. It also explains how modern models, like ABAC and ReBAC evolved from more basic patterns, like RBAC and ACLs.
Motivation
This new link is special because...
Affiliation
Self checks