Forum Discussion
OWA 2013 SSO failed
Glad you could get it working. By LTM logic, do you mean the iRule? This is just necessary to forward the requests for the different Exchange protocols to the virtual server on your internal LTM.
With Exchange 2010, we inject an HTTP header that includes the APM session ID that the LTM can use to persist sessions; however, persistence isn't required in 2013 so you could probably just assign a default pool to your APM VS that points to the LTM.
When you go to "/owa", CAS redirects you to the encoded URL you have above. IIRC, your version of APM won't match an encoded URL to its non-encoded counterpart, or do wildcard matching.
Does the value you have for APM Logout URI match the URI users click to log out?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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