This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi, wondering if I really need a JavaScript policy for what I'm doing.
I'm taking some claims from one JWT and put them into another, but
having issues with claims that are an array.The JWT payload looks like
something this { "sub": "user@example.com...
We've been trying out the KVM API for Apigee X but have noticed a very
strange feature.You can create key value maps and entries in
non-existent environment. While this isn't an issue, I wonder is it an
intentional design decision?It did make debuggi...
Does anybody know if this is a bug with Apigee or a mistake in the
documentation?The docs say:"Enclose variable names in curly braces { }.
If the variable does not exist, an empty string is returned in the
output"source:
https://cloud.google.com/apig...
Is there any way to "loop through all headers" with the AssignMessage
policy? It seems not, as you must specify the header name explicitly,
but I wondered if there's a better way to achieve what I'm doing.My goal
is to redirect" any backend URLs that...
As it seems there is indeed a need for a workaround, I thought it might
be helpful to share the JavaScript snippet I ended up using.So the flow
steps look like this: DecodeJWT-OriginalToken
JavaScript-MapClaimsArrayToCsv
GenerateJWT-NewToken The Java...
@imesh it seems like we might just be able to use the proxy.client.ip
flow variable.Just wondering if there are any issues with that?I did
some checking with our setup:Client --> External HTTP Load Balancer
--[via Network Bridge VMs]--> Apigee XClien...
Same issue, it seems has no effect with
FlowCallout.It seems the best solution is to use the firstnonnull
message template function:
{firstnonnull(a.variable-that-does-not-exist,)}
my-shared-flow-v0
