Application NameOutlook Web Access 2003 - Form Auth
PublisherMicrosoft
Date Entered08/17/2010
Date Modified02/20/2011
webNetwork Version 6.0.1.0
Delivery MethodVirtual server
ConfigurationHost Address : owa.example-cloud.com
Host Port : 443
Web App Type : Virtual
Virtual DNS Name : wnowa.example-cloud.com
Startup URL : /OWALogin
Secure by IP : off
Rewrite Browser Cookier : on
Internal Servers Requires SSL : on
HTTP Headers : Front-End-HTTPS:on
Authenticate Type : Form
Form Type : Server
Form Name : logonForm
Form Trigger : /OWALogin
Form Action : /exchweb/bin/auth/owaauth.dll
Error Trigger : /exchweb/bin/auth/owalogon.asp?url=https://myvirtualname.example-cloud.com/Exchange/&reason=1
Error Page : /docs/owalogout.html

Form Inputs :
flags:4
username : username-attribute
password : password-attribute
youSubmitCreds : Log On
forcedownlevel : 0
trusted : 4
destination : https://wnowa.example-cloud.com/Exchange/@@username-attribute@@
 
Notes

Host authority has to be Enabled so requests made to the internal web server will have the Virtual DNS Name of the web application placed in the HOST HEADER.

If you are using Exchange SP1, then use the following Error Trigger:
/exchweb/bin/auth/owalogon.asp?reason=1

You have to create the owalogout.html on the relay. You will need webNetwork5 HF2 for this to work.

The attr:samaccountname on the destination variable is optional. Unless you need to force what inbox to open up.

The combination for the various Premium/Basic and Public/Private is as follows:
Premium/private - flags=4 forcedownlevel=0 trusted=4
Premium/public - flags=0 forcedownlevel=0 trusted=0
Basic/public - flags=1 forcedownlevel=1 trusted=0
Basic/private - flags=5 forcedownlevel=1 trusted=4

Your OWA system may not require the domain name, or may need your email address.
To catch the log off button so it does not kill the portal cookies create a form and fill in the error trigger and error page.
Error Trigger: /exchange/.*/?Cmd=logoff
Error Page : https://portal.company.com/util/closeDojoWindow.html