Re: How are you guys allowing OWA?

Hi, thanks for the replies. I think I need a little more help on this. I
thought I could access just by typing in https, but apparently I need to do
something in IIS. Do I need to do to follow the steps below this in order to
enable HTTPS, or is there something else I need to do?

Help, I'm confused...

--------------------------------------------
Configure Folder or Web Site to Use SSL/HTTPS
This procedure assumes that your site has already has a certificate assigned
to it. 1. Log on to the Web server computer as an administrator.
2. Click Start, point to Settings, and then click Control Panel.
3. Double-click Administrative Tools, and then double click Internet
Services Manager.
4. Select the Web site from the list of different served sites in the
left pane.
5. Right-click the Web site, folder, or file for which you want to
configure SSL communication, and then click Properties.
6. Click the Directory Security tab.
7. Click Edit.
8. Click Require secure-channel (SSL) if you want the Web site,
folder, or file to require SSL communications.
9. Click Require 128-bit encryption to configure 128-bit (instead of
40-bit) encryption support.
10. To allow users to connect without supplying their own certificate,
click Ignore client certificates.

Alternatively, to allow a user to supply their own certificate, use
Accept client certificates.
11. To configure client mapping, click Enable client certificate
mapping, and then click Edit to map client certificates to users.

If you configure this functionality, you can map client certificates
to individual users in Active Directory. You can use this functionality to
automatically identify a user according to the certificate they supplied
when they access the Web site. You can map users to certificates on a
one-to-one basis (one certificate identifies one user) or you can map many
certificates to one user (a list of certificates is matched against a
specific user according to specific rules. The first valid match becomes the
mapping).
12. Click OK.


--------------------------------------------






"Leythos" <void@xxxxxxxxxxx> wrote in message
news:MPG.1d7840af84930200989d20@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> In article <eThh6xcqFHA.3160@xxxxxxxxxxxxxxxxxxxx>,
> jmcbee@xxxxxxxxxxxxxxxxxx says...
>> As Jim said, you are better opening up port 443 ONLY and requiring your
>> users to type in HTTPS. It sometimes requires some support to get the
>> users
>> used to that.
>
> Or, set the default HTTP site to redirect to the HTTPS connection. In
> fact you can setup email.company.com and have it redirect to the
> https://company.com/exchange if you want.
>
>
> --
>
> spam999free@xxxxxxxxxx
> remove 999 in order to email me


.

Relevant Pages