-
Bug
-
Resolution: Done
-
Critical
-
2.10 GA
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Yes
-
+
-
Undefined
-
Currently, when using APIaaP (APIs as a Product) some policies are broken because Routing policy is
always first. For example, when using Upstream policy, the Upstream policy will
never be reached at all, because Routing policy is first.
The best logic, IMHO, is to place the Routing policy just above the Apicast policy, so user can move the policy and allow users to do what they need.
Example policies right now:
Routing Liquid JWT claim check Apicast
how it should be:
Liquid JWT claim check Routing Apicast
Second example:
Routing Liquid Apicast JWT claim check
Should be:
Liquid Routing Apicast JWT claim check
- blocks
-
THREESCALE-6312 Liquid Context Debug Policy not working with APIaaP
- Closed
-
THREESCALE-6410 JWT Claim Check Policy does not work with APIaaP Backend
- Closed
-
THREESCALE-6834 Routing policy is changing the encoding of some characters in the upstream path
- To Develop
- relates to
-
THREESCALE-7617 Role check policy should be documented as "always place before routing policy"
- Closed