N2H2 access control rules are not being enforced.

  • Document ID:3271505
  • Creation Date:17-Oct-2006
  • Modified Date:26-Apr-2012
    • Micro Focus Products:
      BorderManager

Environment

Novell BorderManager 3.7
Novell NetWare 5.1 SP4
Novell NetWare 6 sp2
N2H2 content filter engine installed
N2H2 access control rules created in nwad32.exe and N2H2 is the enabled vendor
Novell BorderManager 3.8

Situation

N2H2 access control rules are not being enforced.

Resolution

DEFECT 000316045 opened

It has been reported to engineering and it has been fixed, changing ACLCHECK.NLM behavior to block access if N2H2 server can not be reached in Novell BorderManager 3.8

The fix is as below:


a) if its a n2h2(Third party URL Filtering) deny rule and n2h2 server is not reachable or returns an error, return a match so bordermanager blocks access

and

b) if its a n2h2(Third party URL Filtering) allow rule and n2h2 server is not reachable or returns an error, return a no match so the next rule can be evaluated


NOTE: Loading aclcheck with /u option will get you back to the old behaviour.

Additional Information

When the N2H2 server, running on Windows or Linux, is down and BorderManager can not contact with it to check the categories, a messages is displayed on the BorderManager server console but ACLCHECK.NLM is not enforcing rules. By default, it will skip N2H2 rules than can not be checked against the N2H2 server till it reach the BorderManager Default Rule. If this one is an ALLOW, then access will be granted for the users.

Formerly known as TID# 10075483