testbed configuration

[Peter Schober]

Kevin Buckley via users <users at shibboleth.net> [2023-09-04 10:37 CEST]:
> I have been trying to re-familiarise myself with the Shibboleth
> eco-system, initially by setting up an IdP+SP pair on a couple
> of machine-local VMs, making use of RFC 1918 range IPs with the
> server names in the 168.192.in-addr.arpa domain so as to make
> it feel less "artificial".

The only machine that needs to resolve the host names to your IDP or
SP is where your web browser runs. So just make up sensible names in
any domain you like and write the necessary entries into your local
hosts file, https://en.wikipedia.org/wiki/Hosts_(file)

> I also have a front-end Apache server, listenting on 443, that
> proxies into the Jetty instance.

Again trying to help simplify this excersise: Why add httpd and
proxing at all? Jetty can also serve as an TLS-enabled web server.
(You could even drop TLS for now if this is merely a test.)

> [proxy_ajp:debug]  [pid 14908:tid 14] mod_proxy_ajp.c(769):     [client 192.168.56.1:41458] AH00895: serving URL ajp://localhost:8080/idp/profile/admin/hello

I'm not aware recent Jetty versions even supported AJP?

-peter