0.7.4 version question

Boundary
1

Hi @jimlambrt
I saw that client IP was added to the inbound request information in version 0.7.4.
In db, session_connection table was added and client_tcp_address could be checked, but still could not be checked in boundary event log.
Isn’t this applied to the boundary event log?

Thanks!

2

You’ll have to configure the listener block to include “x-forwarded” options so Boundary knows what to trust upstream for setting client_ip.

Unfortunately, those listener config options haven’t been documented in Boundary yet, but you can find the support config options in Vault’s documentation.

I will add documenting these new listener config options to our to-do list.

3

Hi @jimlambrt
I added the following settings to the listener of the worker server. But I couldn’t see the values ​​of the session_connection table in the log.
Thanks!

worker config

  x_forwarded_for_authorized_addrs = "10.0.0.0/8"
  x_forwarded_for_reject_not_authorized = "false"
  x_forwarded_for_reject_not_present = "false"

db session_connection table

1
12064×138 13.2 KB

kibana field

image
image554×1454 67.2 KB

4

Hi @jimlambrt
Am I correct that I can’t check the client_tcp_address in the log?
Or am I setting it up wrong?

Thanks!

5

I solved it by setting the x_forwarded setting to the controller.