Wildcard rules created with the CLI do not follow consistent behavior. (NETIQKB45675)

  • 7745675
  • 02-Feb-2007
  • 14-May-2007

Resolution

fact
Directory and Resource Administrator 7.5

symptom
Wildcard rules created with the CLI do not follow consistent behavior.

symptom
The Command Line Interface acts differently when I include wildcards in place of a group name.

symptom
When I add Group Rules to an ActiveView using an asterisk as part of a command line, the CLI rule is created one way if there are no matches or multiple matches than it does if there is only one match.

cause
Before creating the rule, the rules engine determines if the wildcard matches one, none, or multiple groups. If the wildcard only matches one group, then the rule is created for that group without using a wildcard. If the wildcard does not match any groups, or if the wildcard matches multiple groups, the rule is created with wildcard.

The rule creation behavior changes when you create rules for Users, Groups and Computers, but not for Domain or OU rules.



fix

NetIQ Technical Support plans for a future release of DRA to provide the ability to force the CLI to create the rule with the wildcard definition regardless of the number of current matches to the wildcard.

The next release of DRA (version 8.0) will have this functionality.



Additional Information

Formerly known as NETIQKB45675

Feedback service temporarily unavailable. For content questions or problems, please contact Support.