In stead of using a proxy server to hide our Content Server (CS) environment behind I'm tasked with building a proxy web page that will act like a proxy server. Users would access this proxy web page instead of directly access our CS server. The proxy web page will make call to the CS server and return the response from the CS server to the browser. I am hitting the SSO brick wall :-). When looking at a browser session, in Developer Tools, where the browser directly accesses the CS server I'm seeing one request to https://ourcsserver/otcs/cs.exe. This request has a payload of OTDSTicket. The response from CS to this request is a redirect to https://ourcsserver/otcs/cs.exe/app. In the whole exchange between the browser, CS server and OTDS Server (for SSO) I am not seeing the OTDSTicket being sent to the browser in any form (as a cookie or otherwise). I even looked at the HAR file of the session and can only find only one instance of the OTDSTicket where it was sent from the browser as a payload in the above request.
Any ideas on how I can capture this OTSDTicket using javascript?
Thanks in advance.
