<html><body><div class="gmail_quote">
<div dir="ltr" class="gmail_attr">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:</div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">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.</div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">I’m embarrassed but grateful to Scott Cantor and his helpfulness to the community on this list.</div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">David St Pierre Bantz</div><div dir="ltr" class="gmail_attr">U Alaska </div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">On Mar 7, 2023 at 11:05:40, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<br>Then you are not looking at a log produced by the server actually responding to the request. That is really the only answer.<br>
</blockquote>
</div>
<br>
<div dir="ltr">
<br>
</div></body></html>