Application Name	Apple Portal
Publisher	Apple
Date Entered	07/30/2013
Date Modified
webNetwork Version	6.1.1.126
Delivery Method	Virtual server
Configuration	Host Object ----------- Host Address : daw.apple.com Host Port : 443 Web Application Object ---------------------- Web App Type : HTTP(S) Virtual Server Virtual DNS Name : apple.example-cloud.com Startup URL : /cgi-bin/WebObjects/DSAuthWeb.woa/wa/classicLogin?appIdKey=bbddf091a7ff4178d2deda57c73e701096e4cd4b7f97545ed8703b3c46f38461&baseURL=http://portal.apple.com/&path=validateUser%3Faction%3Dlogin Rewrite Browser Cookies : Enable Internal Servers Require SSL : Enable Single Sign On -------------- Form Type : Client Form Name : appleConnectForm Form Trigger : /cgi-bin/WebObjects/DSAuthWeb.woa/wa/classicLogin\?appIdKey=.*&baseURL=.*&path=validateUser%3Faction%3Dlogin Script : document.forms[1].submit(); Form Method : Post Form Inputs : theAccountName : YOURUSERNAME theAccountPW : YOURPASSWORD
Notes

For this one, it looks like we can get away by proxying the login page, triggering a client side sso form that changes the POST back to the public address (daw.apple.com) and then allow it to go from daw.apple.com back to portal.apple.com like it wants to. This is actually the best case scenario for a public web application - proxy it just long enough to get authenticated then let it go back to its public address - meaning the rest of the web application is NOT proxied.