Branching beyond the simple concept of If/Then
statements, let’s break
policy down into each part you can interact with keeping an eye on the editing
screen for a policy displayed in Figure 8.1, “CLM Server Policy Example”.
Each policy must have at least one constraint. When a constraint is fulfilled, a policy violation occurs. A constraint itself consists of the Constraint Name and at least one condition. Make sure it clearly identifies the conditions that you have added for the Constraint.
The then
part of an if-then statement. The action chosen here will
be taken when the policy constraint and its associated conditions have been met.
When viewing policy violations counts, please keep in mind that despite the number of constraints fulfilled, only one policy violation is counted. |
Now that we understand the different attributes of an individual policy, you’re likely eager to create your own policy. However, we suggest you consider importing our Sample Policy Set, which we’ll tackle that next in the next section. Feel free to create your own policy at any time though.
Terms of Service Privacy Policy
Copyright ©
2008-present, Sonatype Inc. All rights reserved. Includes the
third-party code listed here. Sonatype and Sonatype Nexus are trademarks
of Sonatype, Inc. Apache Maven and Maven are trademarks of the Apache
Software Foundation. M2Eclipse is a trademark of the Eclipse Foundation.
All other trademarks are the property of their respective owners.
Sonatype Headquarters - 8161
Maple Lawn Blvd #250, Fulton, MD 20759
Tysons Office - 8251 Greensboro Drive #610, McLean, VA
22102
Australia Office - 5 Martin Place, Level 14, Sydney 2000, NSW, Australia