Release stytch-go v12 with new RBAC features #158
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
stytch.Client
, notstytchapi.API
orb2bstytchapi.API
.b2b.SessionsClient
, for example) have updated fields in their New methods to make creation more obvious (and remove requirements around doing things like setting a JWKS after the struct has been instantiated). This shouldn't affect any user of the library, but is technically a breaking change. Like the previous point, in the future if we change this interface, we will not count it as a MAJOR version update. This class should be considered an implementation detail to any external users of the library. The expected entry point for consumers of this library is viastytchapi.API
orb2bstytchapi.API
and instantiating something like ab2b.OrganizationsClient
directly is not supported.$METHODRequestOptions
field – this is used to supply authorization data for RBAC (see previous point).AuthenticateJWT
andAuthenticateJWTLocal
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.LazyCache
(which is intended to only be exposed internally) that is used for fetching the project's RBAC policy only when needed – by default this expires every 5 minutes, but only refreshes upon receiving a request that will use the value. This means that if your project does not use RBAC, the cache will never fetch the policy.