NOTE
The concept described in this section could easily be extended to create multiple presences
for an organization, depending on the type of service being set up??”for example,
owa.companyabc.com, oma.companyabc.com, eas.companyabc.com,
rpc.companyabc.com, pop.companyabc.com, imap.companyabc.com, and the like. The
only limitation is the number of IP addresses and certificates that can be created.
Configuring ISA Server to Secure RPC over
HTTP(S) Traffic
The techniques used to configure publishing rules for RPC over HTTP(S) are slightly different
techniques than those used with the OWA, OMA, and ActiveSync publishing rules, but
22. Check the box to enable HTTP connections, and configure HTTP to HTTP
Redirection, as shown in Figure 13.12. This will allow for all HTTP traffic to be automatically
redirected to HTTPS traffic. Click OK to save.
362 CHAPTER 13 Securing Messaging Traffic
the basic idea is still the same: to provide for reverse-proxied HTTP(S) access through the
ISA server, to secure the traffic sent back to Exchange. Before RPC over HTTP(S) can be
secured with ISA Server, it must first be enabled in the Exchange topology.
Pages:
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594