We're using the owaauth.dll to authenticate and connect to OWA from our portal at our company.
It works fine in a straight Exch 2003 only environment. Now we're migrating from Exch 2003 to Exch 2010. Both environments are active and up right now and we're testing. Here's the path to the dll in 2010 (it's slightly different in 2003) https://CasServer.domain.com/owa/auth/owaauth.dll. Here are the parameters we're passing to this dll. username=TD/<USERNAME> password=<PASSWORD> destination=https://CasServer.domain.com/owa/ flags=4 When accessing 2010 mailboxes, using the above method, authentication happens silently and everything works fine, as it did in the 2003 only environment. The resulting url for this method, as shown in the browser, is: https://CasServer.domain.com/owa/ When accessing 2003 mailboxes, using the same method, the authentication works at the CAS server, then is redirected to the legacy url, where the user is prompted by the standard OWA authentication page. The url is: https://legacy.domain.com/exchweb/bin/auth/owalogon.asp?url=https://legacy.domain.com/exchange&reason=0 Does anyone know of a way to silently authenticate when the url is redirected to Legacy? Thx in advance --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
