JWT scope-policy mapping support added #1943
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.
added changes for #1834
for JWT middle-ware:
jwt_scope_to_policy_mapping
in API definition (payload in endpoint to create API as well) - which is just mapping scope-to-policy_idper_api
partitions flag - they shouldn't have the same API id in ACL and might specify limit on API level per API in ACLfor open ID middle-ware:
scope_field_name
andscope_to_policy_mapping
scope_field_name
andscope_to_policy_mapping
are populated it acts as a trigger to use new logic for scope->policy mapping, if those fields are empty it tries to use old logic with client_id->policy_id pairper_api
partitions flag - they shouldn't have the same API id in ACL and might specify limit on API level per API in ACLWe should also re-vendor
tyk/apidef
in dashboard (new fields) if we go forward with that approach