Newbie question - how to test a new shibboleth installation

IAM David Bantz dabantz at alaska.edu
Mon Aug 14 17:26:09 UTC 2023


 Is your IdP servlet perhaps on a different port (8443 is common)?

If so, then something like curl -s -k 'https://localhost:8443/idp/status
<https://localhost/idp/status>’

Haven’t followed this thread carefully, so apologies if this is not helpful.

David St Pierre Bantz

On Aug 14, 2023 at 08:55:44, David Dellinger via users <users at shibboleth.net>
wrote:

> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230814/fa1126f7/attachment.htm>


More information about the users mailing list