Forum Discussion
Jamie_50833
Nimbostratus
Jul 06, 20102010 OWA not automatically logging in
I've added a new Outlook Web Access (OWA) resource on my FirePass for a new 2010 Exchange setup. The 2003 OWA performs auto-login but the new one asks for credentials. Has anyone encountered this?
8 Replies
- Mike_61719
Cirrus
What authentication do you have on the web site (OWA)? - Jamie_50833
Nimbostratus
The new and old OWAs uses basic and integrated windows authentication - Jamie_50833
Nimbostratus
actually the authentication is just basic on the new one. - Mike_61719
Cirrus
What version of Firepass and did you do the following:
Create a new Web Application link (Choose Web Application Type as OWA).
Go to Content Processing and move to the Feature Web Applications section. Check the box labeled "Automatically detect hosts for OWA"
Go to Master Group settings and go to the section labeled NTLM and Basic Auth Proxy. Choose the appropriate settings and try again.
Let me know! - Jamie_50833
Nimbostratus
In what version of Firepass does the "Automatically detect hosts for OWA"
check box appear. I'm running 6.3 with no plan to upgrade it this year.
Also the new OWA 2010 is using forms based authentication, the OWA 2003 was Windows auth. - Mike_61719
Cirrus
I know 6.0.3.2.1 has this included.
6.0.3 is out of support, if you have any issues you will be forced to upgrade. - Jamie_50833
Nimbostratus
I got it to work!
SOL8962 applies to OWA2007 -http://support.f5.com/kb/en-us/solutions/public/8000/900/sol8962.html?sr=10194997
OWA2010 is similar but uses different URL variables which I discovered using live httpheaders capturing an authentication directly to the OWA URL
In the URL field I used:
destination=https://[OWA2010_Root_URL]/owa/&flags=0&forcedownlevel=0&trusted=0&username=%username%&password=%password%&isUtf8=1
Everything else in the solution applies. - bjennis_8288
Nimbostratus
I'm getting HTTP 400 Bad request ERROR using these settings, Exchange 2007 works perfectly. Any idea what this could be in OWA 2010?
Is working for me now, needed to check "Use POST for URL variables:" on the Web Application. (That is what I had also on OWA 2007 webapp)
And what i needed to add (this is the fault of our Exchange config that needs te be fixed) is the domain name. See [DOMAINNAME] and replace it with your domainname.
destination=https://[OWA_SERVER_URL]/owa&flags=0&forcedownlevel=0&trusted=4&username=[DOMAINNAME]\%username%&password=%password%&isUtf8=1
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
