Windows IT Pro Webinar: Raising Exchange Data and Application Availability
Thursday, June 16, 2005 at 12pm EST
Raising Exchange Data and Application Availability
Paul Robichaux, Principal Engineer, 3sharp, an MCSE, and an Exchange MVP
Patrick LaPorte, Product Manager - Windows, VERITAS Software
William Lefkovics on May 19, 2005 at 09:25 PM in Events
« Small Business Server Service Pack 1 Released | Main | Free eBook: The Definitive Guide to Exchange Disaster Recovery and Availability »
TrackBack URL for this entry:
Listed below are links to weblogs that reference Windows IT Pro Webinar: Raising Exchange Data and Application Availability:
We are using MS Server 2003, Exchange server 2003 and IIS 6
The OWA Login.asp page is using POST to transfer the username,password, destination and flags fields to the owaauth.dll.
This is the default process:
Login.asp ====> owaauth.dll ====> OWA
This DLL verifies the data and opens the OWA for the user.
We modified the Login.asp.
We are using the POST to send the fields to our OTPVerify.asp.
That is the new process:
Login.asp ====> OTPVerify.asp ====> owaauth.dll ====> OWA
The OTPVerify.asp is simple. It does some checks on the fields and then - we want the OWA to open.
The OTPVerify.asp runs on the server side.
What we did, is try to do: Server.Transfer to the owaauth.dll - that did not work.
We then tried to use MSXML2.ServerXMLHTTP to POST the data to the owaauth.dll - and we got - Access Denied
We need the asp script that will open the OWA after we did our own checks at the server side.
'Our code is here.
' Then we want to open the OWA, so we try to POST to it.
password = Request.Form("password")
destination = Request.Form("destination")
flags = Request.Form("flags")
info = "&username=" & username & "&password=" & password & "&destination=" & destination & "&flags=" & flags
Set objSrvHTTP = Server.CreateObject ("MSXML2.ServerXMLHTTP")
objSrvHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objSrvHTTP.setRequestHeader "User-Agent", "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"
That did not work.
We'd appreciate any idea - this is pretty urgent for us...
We think there may be 2 types of solutions:
1. Find why the above does not work - and make it work. That is - maybe there is a different way to POST or open the DLL.
2. Bypass the DLL. Is there a way, to open the OWA for somebody without having to use that OWAAUTH.DLL ? Each person has a Password and ID, and we get them from the Login.asp
We recently received the following answer:
you can consider running ASP.Net 2.0 DefaultHttpHandler on IIS6 (which call HSE_REQ_EXEC_URL underneath the covers, but you can write managed HttpHandler to access it)
But we don't know were to start.... we are looking for samples. SOmebody must have done somthing similar.
Looking forward to hearing from you.
Posted by: Arnnei at May 23, 2005 2:56:14 AM
Operating systems are a great help for all industries, I like musho read this type of operating system issues, I wonder if anyone knows about disadvantages of Windows 7, because I am unsure of using it, thanks!
Posted by: buy viagra at Apr 9, 2010 9:06:21 AM