Release stytch-ruby v7 with new RBAC features #107
Merged
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.
RBAC
Other changes
authenticate_jwt_local
will now marshal the decoded JWT into a session to be consistent withauthenticate_jwt
.authenticate_jwt
andauthenticate_jwt_local
now accept an optionalAuthorizationCheck
parameter for performing RBAC checks. These will use a cached version of the project's RBAC policy in order to make an authZ verdict.B2B sessions objects now hold a
LazyCache
that keeps track of the project's RBAC policy. This will only refresh the policy when using local JWT authentication with an authorization check. In other words, if your project does not use local JWT auth with RBAC checks, the cache will never fetch the policy.magic_links.email.invite()
.