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
199 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 125 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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
Find out what you should include to make the best professional email signature for your organization.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

813 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now