Does digiRunner Support X-Forwarded-For for Source IP Identification (API Registration Use Case)?

[EX0429]

Hi community,
We’re placing digiRunner behind a load balancer and need to capture the original client IP for security and testing.

Right now digiRunner only sees the LB IP.

• Does digiRunner support the X-Forwarded-For header for identifying real client IPs?
• If yes, how should it be configured?

Thanks!

[TPIsoftwareOSPO]

Hi , thanks for asking
— this setup is super common when using load balancers, so happy to clarify!

✅Yes, digiRunner supports X-Forwarded-For, and it can be used for both routing and IP-based access control.

Here’s the simple breakdown:

• digiRunner can read the client IP from the X-Forwarded-For header.

• This works whether you're doing traffic rules (like region-based routing) or client IP validation.

• Your load balancer must pass the header correctly; otherwise digiRunner only sees the LB’s IP.

If you need the exact steps for API registration rules or client IP binding, you can search “X-Forwarded-For”, “IP Binding”, or “Source IP Diversion” in the documentation center:
https://docs.tpi.dev/

🔎 Extra tip:
Misconfigurations often happen when the LB doesn’t forward the header, so always verify this part first.
Happy to check your config if you want to share your setup details!