Shibboleth SP3, TCPListener's clientAddress & Kubernetes

[Sandro Mathys]

On 28.01.21, 15:13, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
>>    It's not the same server, otherwise I would definitely not mess with the TCPListener :)

> Then you're done anyway, that's never going to work. It doesn't scale. The SP is not meant to be split that way in its current form.

As far as I've read it should be fine as long as network latency is low?

> The variable replaces both settings because it doesn't matter what they're set to in the file. The clientAddress setting was created for some purpose that I can't even recall because it doesn't do anything obviously useful. If you're not sharing a file between the two, then address alone works, and if you were sharing the file, I can't think of any situation where they'd be different.

Hm, so far I just put the identical config file on both servers. But of course, you're right, I can ignore the clientAddress and just set the address to different values on the two servers. That definitely makes the workaround easier, appreciate the thought!

Thanks,
Sandro