Forum Discussion
Sundar_Sivasank
Nimbostratus
NimbostratusiApp exchange 2013 Login issue
I am using the latest iApp deployment guide for exchange 2013 on LTM v11.5. I see that the iApp doesnt add any persistent profiles for owa. After i just use the iApp to deploy and try to login to my ...
I found the info from the last time I encountered this problem. Are you doing SSL bridging? If so, do the certificates on your CAS contain the host name used to access OWA, and do they both match the cert you're using to decrypt on BIG-IP?
I found the info from the last time I encountered this problem. Are you doing SSL bridging? If so, do the certificates on your CAS contain the host name used to access OWA, and do they both match the cert you're using to decrypt on BIG-IP?
Sundar_SivasankHi Mike, First of all thanks for your response. Yes we are doing SSL Bridging. Currently, all the certs we are using are self signed certs and as mentioned by you the certificates arent the same. So to confirm, i need to have the same certificate/private key as the OWA server on my Big IP for decrypting? Is my understanding correct?- That's correct. You can use a self-signed cert, but you need to copy it to and import it on all your CAS, as well as the BIG-IP.
- Sundar_SivasankThanks Mike. Just another clarification, can i know why exactly there is no need for persistence in Exchange 2013? Is it because of the exchange 2013 behaviour? Also how does the certificate really impact the persistence? Thanks Sundar
- This explains why better than I can: http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx OWA 2013 with FBA uses the SSL private key to identify the session, rather than the session cookie.
- Sundar_SivasankThanks mike will check out the link. Regards Sundar