Newbie question - how to test a new shibboleth installation

[David Dellinger]

Agreed. Thanks!
I viewed the access-control.xml file from the running container and see
that it is indeed allowing localhost.

        <entry key="AccessByIPAddress">
            <bean id="AccessByIPAddress"
parent="shibboleth.IPRangeAccessControl"
                p:allowedRanges="#{ {'127.0.0.1/32', '::1/128'} }" />
        </entry>

I don't want to allow more hosts than necessary. I do want to check the
installation before moving forward.
It might be what Paul mentioned earlier in the thread about NAT. The status
page might be viewable only from within the container's localhost. I'm
seeing a new podman0 interface, but I get a 404 from a tomcat instance when
I hit that interface. It's at least not an access denied message. I don't
have tomcat running at the VM level, so I think I'm hitting tomcat inside
the container.

*David Dellinger *| Sr. Systems Administrator

*Information Technology Services*ddellinger at oxy.edu | T 323-259-1315

*OXY*
*Occidental College*Mary Norton Clapp Library | 1600 Campus Road  |  Los
Angeles, California 90041
oxy.edu/its


On Mon, Aug 14, 2023 at 9:06 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > The container config burn-in doesn't have access-control as one of the
> items
> > that are available, at least in the vanilla build from/for InCommon.
>
> That approach in no way constrains your ability, and in fact need, to be
> able to customize any and all configuration files.
>
> The entire configuration is, and always must be, entirely controlled by
> you.
>
> -- Scott
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230814/8e55fd74/attachment.htm>