logs (finally) matching resolver test!

[IAM David Bantz]

 For a second I thought this was a snarky answer, but I’ve learned to take
Scott very seriously. We all should, as my mea culpa will illustrate:

A few seconds later it hit me: I am looking on the right VM where my
standby IdPs live, BUT I have multiple IdP environments, and my exerciser
curl command was addressing port 18443 (a non-prod instance) rather than
production environment 8443. Of course that is the reason I saw no log
entries (in the production instance). And the reason some users had no SAML
output from the resolver exerciser on that non-prod port is - duh - they
have no identity in the non-prod instance. Changing the resolver request to
point to the correct port for the prod server removed the “inconsistent”
behavior I reported.

I’m embarrassed but grateful to Scott Cantor and his helpfulness to the
community on this list.

David St Pierre Bantz
U Alaska

On Mar 7, 2023 at 11:05:40, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>
> Then you are not looking at a log produced by the server actually
> responding to the request. That is really the only answer.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230307/bbb37514/attachment.htm>