Log out from OWA 2003 also logs out from WebVPN session

[stuart-anderson]

Hi all,

I have a VPN3005 configured so that users can access Outlook Web Access 2003 (amongst other things) via a link on the WebVPN home page. This works fine until the user logs off from OWA by clicking on the "Log Off" icon in OWA. The displayed page is the OWA "You have logged off..." page as expected, but if the user then clicks on the home icon on the WebVPN floating toolbar they are presented with the WebVPN "Your session has been terminated" page, as though they had logged off from their WebVPN session. This is not happening 100% consistently - I'd say it happens half the time, and the other half everything is fine.

The VPN concentrator is running 4.7.2G.

Anybody got any ideas why this might be happening?

Thanks in advance,

Stuart

[ebreniz]

Probably you are hitting the bug CSCec65416 .

[stuart-anderson]

Thanks for the reply. As far as I can see that bug is in the 4.1.n software stream, but it is not mentioned in the release notes for the 4.7.n stream (we're running 4.7.2G) so I presume is not present.

Anybody know otherwise, or got any other thoughts on this?

[derekjfox]

Hi Stuart,

I don't have an answer to your problem as I too have the same issue on the 3030 running 4.7.2G.

Wonder if you can help with an issue I have running OWA through the WebVPN. We were using OWA via http but have now changed the OWA server to ssl/https. I've changed the config for the link to OWA on the 3030 to https but now the link to OWA fails - no error message. Any ideas on why it doesn't work with https?

Derek

[stuart-anderson]

Hi Derek,

On the advice of our support partner, who had in turn been speaking with Cisco, I changed to the 4.1.nnn code stream and the OWA logout problem has disappeared - apparently Cisco acknowledged that this is a bug in the 4.7.nnn code stream. I'm not currently using the extra features of 4.7 so changing code wasn't a problem, but you may not be so lucky!

Regarding the https issue, I experienced a similar thing a while back, although I did get to a login box but just couldn't authenticate (this had been fine via http), and overcame it by setting the OWA server to use basic authentication only (i.e. not to try and use NTLM). Although this means that user credentials are sent in clear text according to Microsoft, I don't think this is a problem security-wise as long as we are using HTTPS only as the whole connection is encrypted.

Hope this helps.

Stuart