We recently deployed IEAs. We're only worried about encrypting the message from point A to point B. We don't require the recipient to enter a password to open the message - it opens automatically.
What we've noticed very recently is users that receive securedoc.html message on their iPhones are having problems opening the message now. We've been able to isolate the problem to folks running the latest iPhone upgrade - 2.2.
Users running 2.2 get a password prompt before the message opens. Users running 2.1 or opening the message on a PC with firefox or IE - the message automatically opens without requiring the user to enter a password.
Anyone else seeing this?
We did also upgrade the IEAs (6.3.04) Saturday, but the common thread seems to be iPhone firmware 2.2.
Anyone else using an IEA and not requiring registration/passwords for securemessaging?
If so, I'd love to hear how you handle these issues. This is something we've been struggling with and would appreciate any pointers.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...