Description shows the mapping between the sample ruleset and the case study.
Table 4–3 Mapping Between Sample Ruleset and Case Study
The order of priority for applying the ruleset is hostname-subdomain-domain.
For example, assume that you have the following entries in the Domain-based rulesets list:
sesta.com|ruleset1 eng.sesta.com|ruleset2 host1.eng.sesta.com|ruleset3
ruleset3 is applied for all pages on host1.
ruleset2 is applied for all pages in the eng subdomain, except for pages retrieved from host1.
ruleset1 is applied for all pages in the sesta.com domain, except for pages retrieved from the eng subdomain, and from host1.
Click Save to complete.
Restart the Gateway from a terminal window:
./psadmin start-sra-instance –u amadmin – f <password file> –N <profile name>– t <gateway> |
Secure Remote Access server supports MS Exchange 2000 SP3 installation and MS Exchange 2003 of Outlook Web Access (OWA) on the Sun Java System Web Server and the IBM application server.
Log in to the Portal Server administration console as administrator.
Select the Secure Remote Access tab, and select the Gateway profile for which you want to set the attribute.
In the Map URIs to RuleSets field, enter the server name where Exchange 2000 is installed followed by the Exchange 2000 Service Pack 4 OWA ruleset.
For example:
exchange.domain.com|exchange_2000sp3_owa_ruleset. |
On the Exchange side Public Folders are configured to use NTLM Authorization. It needs to be changed to use HTTP Basic Authorization.
To do this, go to the Exchange server and select the Control Panel-->Administrative Tools, then open Internet Information Services.
Under Default Web Site there is a tab for Public Folders called Public. Right Click and select properties. Click on Directory Security Tab. Select "Edit.." on the Anonymous Access and Authentication control panel. Unselect everything else and select only Basic Authentication.