Configuring Services for Subscribers

You can configure services to control subscriber traffic in response to IVE Host Checker policy compliance by a subscriber’s machine.

To configure services to check hosts for subscribers:

1. Configure a policy to check hosts for a subscriber. For a host-checking policy, specify policy rules for subscribers to redirect the subscriber’s HTTP traffic to the IVE Host Checker or to the captive portal.

   For a sample policy that slows all subscriber traffic and forces all Web traffic to a redirect server with the specified address, which then redirects the traffic to the IVE Host Checker server, see policyGroupName=hostcheck, ou=hostchecker, o=Policies, o=umc in the sample data.

   For a sample policy that slows all subscriber traffic and forces all Web traffic to a redirect server with the specified address, which then redirects the traffic to the Host Check Result portal, see policyGroupName=block, ou=hostchecker, o=Policies, o=umc in the sample data.

2. Create a scope for the services that define actions to be taken in response to IVE host-checking results.

   For a sample scope, see l=HC-Subscriber, o=Scopes, o=umc in the sample data.

3. In the scope you created in Step 2, create a service that defines actions to be taken in response to the IVE host-checking results. Then set the type to normal, and specify the policy group configured in Step 1.

   For a sample service that redirects traffic to the IVE Host Checker server, see serviceName=HostCheck, l=HC-Subscriber, o=Scopes, o=umc in the sample data.

   For a sample service that redirects traffic to the Host Check Result portal, see serviceName=Block, l=HC-Subscriber, o=Scopes, o=umc in the sample data.

4. Assign the scope to a subscriber folder to make the service available to the subscribers.

   For a retailer, specify any plug-ins that the subscribers in the domain might use, and specify a service that would be applied to subscribers who do not belong to a specific group of subscribers.

   For a sample subscription that performs host checking for a retailer, see retailermame=SP-HC, o=Users, o=umc in the sample data.

5. Create service subscriptions for subscribers. To allow all subscribers in the folder to inherit the subscription, create a subscription at the folder level. For a subscriber, create any objects that might apply to the group of subscribers, such as service subscription, service schedule, or subscriber.

   For a sample subscription that automatically performs host checking when the subscriber logs in, see serviceName=HostCheck, ou=CheckOnLogin-Subscribers, retailermame=SP-HC, o=Users, o=umc in the sample data.

   For a sample subscription that performs host checking that is activated according to a service schedule, see serviceName=HostCheck, ou=CheckOnSchedule-Subscribers, retailermame=SP-HC, o=Users, o=umc in the sample data.

   For a sample subscription that performs host checking that is activated according to a Quota VTA plug-in, see serviceName=HostCheck, ou=VTASched-Subscribers, retailermame=SP-HC, o=Users, o=umc in the sample data.

   For a sample subscription that redirects all other subscribers for this retailer to the captive portal, see serviceName=Block, retailermame=SP-HC, o=Users, o=umc in the sample data.

Figure 6 shows the SDX Admin navigation pane with the retailer used in the sample data.

Figure 6: Sample Retailer Configuration for Host Checking

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.