The client.cn is not propogated when proxy A calls proxy B

[#1]

Hi All

We notice that when we use mutual TLS our consumer's client.cn is not propagated when we call a local proxy, i.e. LocalTargetConnection. Is this by design or are we doing something wrong? Please advise?

We are using the SAP branded private cloud version of Edge 4.17.01.01

[DChiesa]

Hi, I think this is by design. Context variables don't propagate to new Proxy invocations. If you would like to propagate them, set them into a header or formparam or query param, etc.

[#3]

Bad design in my opinion. Losing the caller's context that way. "client.cn" is a read-only flow variable which is nice for security purposes. Now we have to hack a workaround and clutter the called proxy with additional logic.