Tamás - In addition to Larry's points about moving config out of gateway-site into topologies, I would like to mention that there are multiple configuration items which allow for gateway-wide defaults in gateway-site.xml, which can be overridden at the topology level. It's possible that your goal can be achieved by following this model as well. Rather than MOVING these configurations, perhaps they could be overridden at the topology level.
I'm actually wondering if those specific configurations really make sense at the topology level, and I would be interested in understanding the motivation better. For instance, topology port mapping seems like a gateway-level configuration to me; I am interested to understand why it makes more sense as a topology-level configuration. Where in a topology would such configurations be applied? They're not really provider or service configurations, right? - Phil On Mon, Nov 17, 2025 at 1:08 PM Tamás Hanicz <[email protected]> wrote: > Hey Folks, > > Knox has a few use-cases where topology specific configuration is stored in > the gateway-site.xml. It would be beneficial if these were moved into the > actual topologies for better understanding and readability. > > Current use-cases I can think of (there might be more): > > - Topology port mapping > - Client auth needed exclusion for specific topologies > - Async-support for specific topologies > > These changes could break things in existing environments, especially port > mapping. What are your opinions on this change? > > JIRA: http://issues.apache.org/jira/browse/KNOX-3213 > > Regards, Tamas >
