Ex: Newbie question - how to test a new shibboleth installation

[David Dellinger]

Hi Michael,

Thanks for your reply. I really appreciate it.
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.
I'll see if I can find more about InCommon's config burn-in, but I may have
to just try to connect to SAML as my validation test.

*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 8:00 AM Michael Young <m.a.young at durham.ac.uk>
wrote:

>
>
> On Fri, 11 Aug 2023, David Dellinger wrote:
>
> > Thanks Paul,
> >
> > I get the same result using curl from the VM that is running the
> Shibboleth
> > container.
> >
> > $ curl --insecure https://localhost/idp/status
> > .snip
> >         <div class="content">
> > You do not have access to the requested resource.            </div>
> > .snip
> >
> > I'm reading through the step-by-step that you sent, and am looking at the
> > samltest site. Thanks!
>
> Access to the idp status is controlled by the conf/access-control.xml
> file, where there will be a line like
>       p:allowedRanges="#{ {'127.0.0.1/32', '::1/128'} }" />
>
> so you need to work out the address shibboleth is seeing (eg. from the
> jetty or tomcat logs) and add that to the line.
>
>         Michael Young
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230814/7fbf1e78/attachment.htm>