Forum Discussion
NimbostratusExchange OWA 2013 SSO
I am trying to deploy OWA 2013 via a portal resource. I have configured the SSO profile for Forms - Client Initiated as per the settings in the manual on AskF5. I have had this work maybe once or twice. Anytime it works, it will only work the first time and will fail if a logoff and re-login are attempted (most of the time it fails the first time as well). It is like it is not detecting the form and therefor not passing the parameters. My form detection is URI and the string is /owa/auth/logon.aspx. Request Prefix and Submit Request Prefix are selected. Any thoughts? Ideas? Thanks.
12 Replies
Makes sense that that would happen. OWA 2013 redirects you to the /owa/auth/logon.aspx page, which is also the URI that causes the form to be detected, thus causing your stored login credentials to be resubmitted.
You might try experimenting with the form detection settings in the SSO configuration. Checking for a header/value or cookie/value pair that only exists in the initial server response, and not in the post-logoff redirect response, for example.
You can also trigger the form detection based on a URI/header/cookie that doesn't exist, using the Request Negative option: http://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-sso-config-11-2-0/3.html
schmuckYeah... good call. Just used to the more generic "Click here to close browser" logoff screen which doesn't exist anymore. I've done some tracing and there appear to be some differences in the logon.aspx page (probably have to use a negative). I'm not too worried though. SSO is working now and that is the default behaviour in OWA 2013 so I say live with it. :)
Thanks for the help. Problem solved.
