<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Here's the link. I can connect to other services, and the reason I'm using the same client.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace"><a href="https://pastebin.com/FgBura6j#mt7M28GH">idp-process-logs-0919-24 - Pastebin.com</a><br></div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">-Jeff</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 19, 2024 at 4:43 PM 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">In point of fact, it sort of makes it look like that client thinks it wants to connect to that IP address URL, and if that were actually true, it should fail when the TLS cert doesn't line up.<br>
<br>
So either the client is broken (very seriously) or that isn't the URL it's trying to reach and it's likely connecting to the expected URL in the OP's metadata.<br>
<br>
The IdP is logging it obviously, so the client's managed to issue the request and get it into the log, so hopefully it used the real URL and not whatever that custom parameter says.<br>
<br>
-- Scott<br>
<br>
<br>
</blockquote></div>