?
Solved

For the best security on an Exchange 2007 deployment, I really don't want to open up port 80 on the firewall. I will be using SSL certificates for OWA 2007 from Verisign.

Posted on 2008-10-10
2
Medium Priority
?
209 Views
Last Modified: 2012-05-05
I am deploying client access servers in exchange 2007. I plan to use SSL cerificates from Verisign with OWA. However, many outside users with legacy web browsers might not be able to connect with https   Are there any functions in OWA 2007 which require http?  I really don't want to expose the internal lan to port 80 if not necessary. An ISA reverse proxy setup will be deployed later, but now we need the client access server behind the inside firewall (not in the dmz) and OWA up and running. I can see the help deskphones ringing off the hook from the external users who can't connect via http if their browsers are not patched.  With only SSL port 443 open with a signed certificate from verisign,, there is a higher security configuration on the OWA deployment.

What is your suggestion?
0
Comment
Question by:bignewf
2 Comments
 
LVL 31

Assisted Solution

by:Paranormastic
Paranormastic earned 500 total points
ID: 22688945
I think you are worrying too much.
SSL has been supported since before IE3.  Pretty much every browser in use today uses 128 bit SSL, if you are really worried about it then just don't force 128 bit SSL so that those that do support it will use 128 bit and those that are ancient and haven't been patched in 7 years can dumb down to an older version of SSL.
Verisign has been around long enough where they should have their root pretty much whereever you go since they date back to the mid-90s.  You're not going to do much better than that and if you are worried about that, there are few alternatives.
Realistically, even the guy running win98 has patched sometime over the last 7 years or so to access their banking site or whatever.  If they are too freaked out to access your SSL page, then they will be entirely too paranoid to supply anything that would require SSL (password, bank info, whatever) and live in a cave.  You will likely cause more of an issue by not having SSL enabled for sensitive pages than worrying about the theoretical user that won't be able to use SSL.
0
 
LVL 15

Accepted Solution

by:
bignewf earned 0 total points
ID: 22688984
Thanks for your answer. That covered everything.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timelineā€¦
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery procedā€¦
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses

588 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question