We have set up a SAML IdP in our gateway for Single Sign On. When loading a session from a browser, I am able to watch the general handshaking via a SAML-tracer. After all the automatic redirects and authentication succeeds, a IdP Session Cookie is created, and dropped into the browser Web Dev Tools/Stroage/Cookies. I can then see the cookie being used in the Perspective Session in a Gateway keepalive call back every few seconds.
My goal is to use this cookie in system.net.httpClient GET calls. My IT department and I could only think to possibly pass this cookie as a IdP attribute in the IdP Response Data. Problem is, it looks like the IdP attribute is not support for SAML, even if we can stuff the desired cookie as an attribute.
So my question is, is there a different way to get the cookie into the session using SAML SSO, because it is being used by the Session for the KeepAlive? Maybe we could use system.net.httpClient to create a new auth Session, but then that is not using the SSO that was already established. Seems like we will need to user to still put in credentials at the start of a session by pinging a URL, redirect to the IdP, have the user re-enter their credentials, and then looking at the cookie manager.
If that is what we have to do, it seems like there is no point to set up SSO with SAML? (For our use case). Probably should just do an Active Directory sign in and pass the log in credentials to system.net.httpClient GET call also?