tailieunhanh - configuring isa server phần 3

nó cũng sẽ có những nhu cầu đặc biệt để bảo vệ mình khỏi sự xâm nhập và tấn công không mong muốn từ các nguồn độc hại và thù địch. Sự phát triển của Internet đã được đi kèm với sự tăng trưởng trong những con số và sự tinh vi của tin tặc và các công cụ có sẵn cho họ. | NOTE You can configure whether the ISA server will cache SSL objects. To do so you must use the FPCWebRequestConfiguration COM object. Normally cacheable Web objects are cached by the ISA server. These steps represent only one possible SSL bridging scenario. Note that a great deal of encrypting and decrypting is going on to maintain the security of the object. SSL Bridging with Incoming Web Requests Let s look at how incoming Web requests are handled. First the ISA server must be configured to listen for SSL requests on the port with which the external client will connect as illustrated in Figure . By default this is port 443. This is done by enabling SSL listeners on the Incoming Web Requests tab of the array s Properties sheet. You have the following options Use the same listener configuration for all internal IP addresses Configure listeners individually per IP address NOTE If you want to use SSL for two different Web servers you need to select the second choice and configure the listeners individually. Figure Configure the Array Properties to Enable and Configure SSL Listeners Additionally a server certificate for Web requests must be specified. If you selected the first option you can now edit the IP address properties. If you selected the second option you might need to first add an IP address before you can configure its properties. In either case you then check the Use a server certificate to authenticate to Web clients check box and choose a certificate from the list. TIP You will not be able to configure this option unless you have certificates installed on the ISA server. For this configuration to work properly each internal Web server should be published on different public IP address and a server certificate mapped to each. Now the incoming Web requests will be handled as follows 1. The external client sends an HTTPS request for a Web object on the internal Web server. 2. ISA Server decrypts the request and terminates the SSL connection. 3. .