-
Notifications
You must be signed in to change notification settings - Fork 188
/
common-policy-3.xsd
2910 lines (2842 loc) · 151 KB
/
common-policy-3.xsd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!--
~ Copyright (c) 2010-2018 Evolveum and contributors
~
~ This work is dual-licensed under the Apache License 2.0
~ and European Union Public License. See LICENSE file for details.
-->
<xsd:schema targetNamespace="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3"
xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3"
xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3"
xmlns:s="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
elementFormDefault="qualified"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
jaxb:extensionBindingPrefixes="xjc"
jaxb:version="2.0">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
<!-- Don't provide schemaLocation here, as it causes xjc to really contact the URIs (!) -->
<xsd:import namespace="http://prism.evolveum.com/xml/ns/public/annotation-3"/>
<xsd:import namespace="http://prism.evolveum.com/xml/ns/public/types-3"/>
<xsd:import namespace="http://prism.evolveum.com/xml/ns/public/query-3"/>
<xsd:import namespace="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3"/>
<xsd:include schemaLocation="http://midpoint.evolveum.com/xml/ns/public/common/common-core-3" />
<xsd:complexType name="PolicyConstraintsType">
<xsd:annotation>
<xsd:documentation>
Set of governance, risk management, compliance (GRC) and similar policy constraints
that influence the identity model. These constraints act as triggers for the rules.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="objectState" type="tns:StatePolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Particular state of the object, described by a filter or an expression.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>PolicyConstraintsType.objectState</a:displayName>
<a:help>PolicyConstraintsType.objectState.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignmentState" type="tns:StatePolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Particular state of an assignment, described by a filter or an expression.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>PolicyConstraintsType.assignmentState</a:displayName>
<a:help>PolicyConstraintsType.assignmentState.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="hasAssignment" type="tns:HasAssignmentPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
The focus has assignment(s) of given object(s).
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>PolicyConstraintsType.hasAssignment</a:displayName>
<a:help>PolicyConstraintsType.hasAssignment.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="hasNoAssignment" type="tns:HasAssignmentPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
The focus has no assignment(s) of given object(s).
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>PolicyConstraintsType.hasNoAssignment</a:displayName>
<a:help>PolicyConstraintsType.hasNoAssignment.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="exclusion" type="tns:ExclusionPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Exclusion constraint. Constraint that forbids this object to be assigned together with other object.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.exclusion</a:displayName>
<a:help>PolicyConstraintsType.exclusion.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="minAssignees" type="tns:MultiplicityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Actual number of objects that have this role assigned is lower than prescribed value.
(The constraint should be perhaps named minAssigneesViolation.)
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.minAssignees</a:displayName>
<a:help>PolicyConstraintsType.minAssignees.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="maxAssignees" type="tns:MultiplicityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Actual number of objects that have this role assigned is higher than prescribed value.
(The constraint should be perhaps named maxAssigneesViolation.)
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.maxAssignees</a:displayName>
<a:help>PolicyConstraintsType.maxAssignees.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="objectMinAssigneesViolation" type="tns:MultiplicityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Actual number of objects that have this object (e.g. role) assigned is lower than prescribed value.
This is the same as minAssignees, but indicates that the constraint should be evaluated against an object
when evaluating object constraints. HIGHLY EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:displayName>PolicyConstraintsType.objectMinAssigneesViolation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="objectMaxAssigneesViolation" type="tns:MultiplicityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Actual number of objects that have this object (e.g. role) assigned is higher than prescribed value.
This is the same as minAssignees, but indicates that the constraint should be evaluated against an object
when evaluating object constraints. HIGHLY EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:displayName>PolicyConstraintsType.objectMaxAssigneesViolation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="modification" type="tns:ModificationPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Constraint that triggers when the object is modified.
Modification of the object (add, modify, delete).
(This constraint should be perhaps named objectModification.)
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.modification</a:displayName>
<a:help>PolicyConstraintsType.modification.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignment" type="tns:AssignmentModificationPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Constraint that triggers when the object is assigned, unassigned or the assignment is modified.
Modification of an assignment, i.e. where this object is a target of assignment that is being modified.
(This constraint should be perhaps named assignmentModification.)
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.assignment</a:displayName>
<a:help>PolicyConstraintsType.assignment.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="objectTimeValidity" type="tns:TimeValidityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
A constraint that triggers when validity of an object or any of its time-sensitive
items (e.g. password) is about to end.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.objectTimeValidity</a:displayName>
<a:help>PolicyConstraintsType.objectTimeValidity.help</a:help>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignmentTimeValidity" type="tns:TimeValidityPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
A constraint that triggers when validity of an assignment or any of its time-sensitive
items (e.g. password) is about to end.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.6</a:since>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.assignmentTimeValidity</a:displayName>
<a:help>PolicyConstraintsType.assignmentTimeValidity.help</a:help>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="situation" type="tns:PolicySituationPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Occurrence of the policy situation within an object or an assignment.
</xsd:documentation>
<xsd:appinfo>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.situation</a:displayName>
<a:help>PolicyConstraintsType.situation.help</a:help>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="collectionStats" type="tns:CollectionStatsPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
<p>
Constraints for collection stats (statistics). Can be used to trigger policy
rules on the number of objects in collection, percentage and so on.
</p>
<p>
Policy rules with this constraint are ignored during normal processing.
Evaluation of such policy rules require special handling (e.g. scanner task).
</p>
</xsd:documentation>
<xsd:appinfo>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.collectionStats</a:displayName>
<a:help>PolicyConstraintsType.collectionStats.help</a:help>
<a:since>4.0</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="alwaysTrue" type="tns:AlwaysTruePolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
This constraint always applies.
</xsd:documentation>
<xsd:appinfo>
<a:since>4.2</a:since>
<a:experimental>true</a:experimental>
<a:elaborate>true</a:elaborate>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="and" type="tns:PolicyConstraintsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Constraints that must all apply. (But note that if there are more values of this item,
they are interpreted according to the enclosing operator.)
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:elaborate>true</a:elaborate>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="or" type="tns:PolicyConstraintsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Constraints from which at least one must apply. (But note that if there are more values of this item,
they are interpreted according to the enclosing operator.)
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:elaborate>true</a:elaborate>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="not" type="tns:PolicyConstraintsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
The inner constraint must not apply.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:elaborate>true</a:elaborate>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="transition" type="tns:TransitionPolicyConstraintType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Specifies how the inner constraints are to be evaluated with regards to operation start and end state.
May not include any transitional constraints itself!
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.transition</a:displayName>
<a:help>PolicyConstraintsType.transition.help</a:help>
<a:elaborate>true</a:elaborate>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ref" type="tns:PolicyConstraintReferenceType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
References another policy constraint e.g. by its name.
The referenced constraint must be present as part of policy rules gathered for a given
assignment or object. Also, all declared global constraints are available for referencing,
regardless of which objects they are attached to or whether they are active or not.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<xsd:appinfo>
<a:displayName>PolicyConstraintsType.ref</a:displayName>
<a:help>PolicyConstraintsType.ref.help</a:help>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
<!--<xsd:attribute name="id" type="xsd:long"/>--> <!-- already present in the abstract constraint -->
</xsd:complexType>
<xsd:complexType name="PolicyConstraintReferenceType">
<xsd:annotation>
<xsd:documentation>
References another policy constraint.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="name" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Name of the constraint referenced.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintReferenceType.name</a:displayName>
</xsd:appinfo>
</xsd:annotation>
<!-- parameters, if the referenced constraint is a parametrized one -->
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:long"/>
</xsd:complexType>
<xsd:complexType name="AbstractPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Basic data structure for all policy constraints.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:schemaMigration>
<a:element>tns:enforcement</a:element>
<a:version>4.0</a:version>
<a:operation>removed</a:operation>
</a:schemaMigration>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="name" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Identifier of the constraint. It is used when midPoint
needs to refer to a specific constraint, e.g. in order
to record exception.
This element is formally specified as optional, mostly
due to the compatibility reasons. But it
has to be provided in order for some functionality to
work correctly.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.5</a:since>
<xsd:appinfo>
<a:displayName>AbstractPolicyConstraintType.name</a:displayName>
<a:help>AbstractPolicyConstraintType.name.help</a:help>
</xsd:appinfo>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="description" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo>
<a:displayName>AbstractPolicyConstraintType.description</a:displayName>
<a:help>AbstractPolicyConstraintType.description.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element ref="tns:documentation" minOccurs="0" maxOccurs="1"/>
<xsd:element name="presentation" type="tns:PolicyConstraintPresentationType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
How should be triggering of this constraint presented, e.g. in enforcement messages,
in approvals, in certification, in notifications, etc.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>AbstractPolicyConstraintType.presentation</a:displayName>
<a:help>AbstractPolicyConstraintType.presentation.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:long"/>
</xsd:complexType>
<xsd:element name="abstractPolicyConstraint" type="tns:AbstractPolicyConstraintType" />
<xsd:complexType name="PolicyConstraintPresentationType">
<xsd:annotation>
<xsd:documentation>
How should be triggering of this constraint presented, e.g. in enforcement messages,
in approvals, in certification, in notifications, etc.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="message" type="tns:LocalizableMessageTemplateType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Message to be conveyed to the user.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintPresentationType.message</a:displayName>
<a:help>PolicyConstraintPresentationType.message.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="shortMessage" type="tns:LocalizableMessageTemplateType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Very short message describing the situation. Could be used for e.g. notification messages subject, approval process or work item names.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintPresentationType.shortMessage</a:displayName>
<a:help>PolicyConstraintPresentationType.shortMessage.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="longMessage" type="tns:LocalizableMessageTemplateType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Long, documentation-like explanation of the rule.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>PolicyConstraintPresentationType.longMessage</a:displayName>
<a:help>PolicyConstraintPresentationType.longMessage.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-- todo something like GUI component id/type -->
<xsd:element name="final" type="xsd:boolean" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
If set to true, no embedded triggers will be presented. Use for hiding constraints that are
to be considered too technical to be shown to user. EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:displayName>PolicyConstraintPresentationType.final</a:displayName>
<a:help>PolicyConstraintPresentationType.final.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="hidden" type="xsd:boolean" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
If set to true, this trigger will be excluded from presentation. EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:displayName>PolicyConstraintPresentationType.hidden</a:displayName>
<a:help>PolicyConstraintPresentationType.hidden.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="displayOrder" type="xsd:int" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Ordinal number that determines ordering of displayed messages. EXPERIMENTAL.
</xsd:documentation>
<xsd:appinfo>
<a:experimental>true</a:experimental>
<a:displayName>PolicyConstraintPresentationType.displayOrder</a:displayName>
<a:help>PolicyConstraintPresentationType.displayOrder.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:long"/>
</xsd:complexType>
<xsd:element name="policyConstraintPresentation" type="tns:PolicyConstraintPresentationType" />
<xsd:simpleType name="TriggeredPolicyRulesStorageStrategyType">
<xsd:annotation>
<xsd:documentation>
How much information about triggered policy rules should be stored?
EXPERIMENTAL
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumClass/>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="none">
<xsd:annotation>
<xsd:documentation>
Triggered policy rules will not be stored.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="NONE"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="messageOnly">
<xsd:annotation>
<xsd:documentation>
Only message and short message for each trigger will be stored. Hidden and final presentation settings are respected.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="MESSAGE_ONLY"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="full">
<xsd:annotation>
<xsd:documentation>
The triggers and other information for the rule will be stored (including subtriggers).
Hidden and final presentation settings are respected.
</xsd:documentation>
<xsd:appinfo>
<jaxb:typesafeEnumMember name="FULL"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<!--<xsd:simpleType name="SituationConstraintsStorageStrategyType">-->
<!--<xsd:annotation>-->
<!--<xsd:documentation>-->
<!--Should triggers for situation constraints be stored "as is" or should referenced rules be unwrapped?-->
<!--EXPERIMENTAL-->
<!--</xsd:documentation>-->
<!--<xsd:appinfo>-->
<!--<jaxb:typesafeEnumClass/>-->
<!--<a:deprecated>true</a:deprecated>-->
<!--</xsd:appinfo>-->
<!--</xsd:annotation>-->
<!--<xsd:restriction base="xsd:string">-->
<!--<xsd:enumeration value="asIs">-->
<!--<xsd:annotation>-->
<!--<xsd:documentation>-->
<!--Triggers for situation constraints should be stored "as is".-->
<!--</xsd:documentation>-->
<!--<xsd:appinfo>-->
<!--<jaxb:typesafeEnumMember name="AS_IS"/>-->
<!--</xsd:appinfo>-->
<!--</xsd:annotation>-->
<!--</xsd:enumeration>-->
<!--<xsd:enumeration value="unwrapped">-->
<!--<xsd:annotation>-->
<!--<xsd:documentation>-->
<!--Rules referenced from situation constraints should be unwrapped.-->
<!--</xsd:documentation>-->
<!--<xsd:appinfo>-->
<!--<jaxb:typesafeEnumMember name="UNWRAPPED"/>-->
<!--</xsd:appinfo>-->
<!--</xsd:annotation>-->
<!--</xsd:enumeration>-->
<!--</xsd:restriction>-->
<!--</xsd:simpleType>-->
<xsd:complexType name="ExclusionPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Container that defines exclusion of entities (e.g. roles).
It is a part of Segregation of Duties (SoD) mechanism.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:displayName>ExclusionPolicyConstraintType.details</a:displayName>
<a:schemaMigration>
<a:element>tns:policy</a:element>
<a:version>4.0</a:version>
<a:operation>removed</a:operation>
</a:schemaMigration>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="targetRef" type="tns:ObjectReferenceType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
<p>
Target of exclusion. The object defining this "exclusion" and
the object defined as target cannot be assigned at the same time.
Filter in the reference may be used to dynamically exclude broader
range of roles - assuming that runtime resolution is used.
</p>
</xsd:documentation>
<xsd:appinfo>
<a:objectReferenceTargetType>tns:AbstractRoleType</a:objectReferenceTargetType>
<a:displayName>ExclusionPolicyConstraintType.targetRef</a:displayName>
<a:help>ExclusionPolicyConstraintType.targetRef.help</a:help>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="orderConstraint" type="tns:OrderConstraintsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Specification of relation(s) when this exclusion constraint should be applied at the source side.
(I.e. this is evaluated against the object defining this exclusion constraint.)
The default is "order = 1".
EXPERIMENTAL. Currently it does not work with non-member relations because of assignment
evaluation optimizations (see TestSegregationOfDuties.test950JackSelfExclusion). So it can
be used only for default and manager relations.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7.1</a:since>
<a:displayName>ExclusionPolicyConstraintType.orderConstraint</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="targetOrderConstraint" type="tns:OrderConstraintsType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Specification of relation(s) when this exclusion constraint should be applied at the target side.
(I.e. this is evaluated against the target object.)
The default is "order = 1".
EXPERIMENTAL. Currently it does not work with non-member relations because of assignment
evaluation optimizations (see TestSegregationOfDuties.test950JackSelfExclusion). So it can
be used only for default and manager relations.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7.1</a:since>
<a:displayName>ExclusionPolicyConstraintType.targetOrderConstraint</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="exclusionPolicyConstraint" type="tns:ExclusionPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="MultiplicityPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Constraint on multiplicity of assigned objects.
(Other multiplicity requirements will be probably treated in separate constraints, like "constraint that
restricts value(s) of given item, based on a set of conditions that must be met".)
</xsd:documentation>
<xsd:appinfo>
<a:container/>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="multiplicity" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Numeric value or string "unbounded".
</xsd:documentation>
<xsd:appinfo>
<a:displayName>MultiplicityPolicyConstraintType.multiplicity</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="relation" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Relation(s) to which this constraint applies. All of these relations must match
the defined multiplicity. If no relation is present, org:default (i.e. null) is assumed.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>MultiplicityPolicyConstraintType.relation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-- TODO something like "assigned" vs. "effective" - i.e. if we watch assignments created
or assignments that are actually "alive" (i.e. enabled and with condition = true) -->
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="minAssigneesPolicyConstraint" type="tns:MultiplicityPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:element name="maxAssigneesPolicyConstraint" type="tns:MultiplicityPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="ModificationPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Constraint that triggers the rule on object modification, addition or deletion.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.5</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="operation" type="t:ChangeTypeType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Specifies the operation(s) for which this constraints should be triggered.
If not specified then it will be triggered for all operations.
This defines the object operation (add/modify/delete of the entire object)
or assignment operation (add/modify/delete of the given assignment).
</xsd:documentation>
<xsd:appinfo>
<a:displayName>ModificationPolicyConstraintType.operation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="item" type="t:ItemPathType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
Specification of items that must be modified (all of them) in order for this
constraint be triggered. If no items are specified then any modification will
trigger this constraint.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>ModificationPolicyConstraintType.item</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="exactPathMatch" type="xsd:boolean" minOccurs="0" default="false">
<xsd:annotation>
<xsd:documentation>
If true, item paths to be matched must match exactly. E.g. if "inducement" is specified
as an item to be matched, then only object modifications having "inducement" in the path
(i.e. whole inducement being added/deleted/replaced) would match.
This is applicable only for modification operations. For add and delete operations the
value of this flag is ignored.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>ModificationPolicyConstraintType.exactPathMatch</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="expression" type="c:ExpressionType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Expression that is used to determine the result. It is evaluated in addition to all the other
conditions, and must have a value of true in order for constraint to be triggered.
</xsd:documentation>
<xsd:appinfo>
<a:since>3.7</a:since>
<a:displayName>ModificationPolicyConstraintType.expression</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!--<xsd:element name="ignoreItem" type="t:ItemPathType" minOccurs="0" maxOccurs="unbounded">-->
<!--<xsd:annotation>-->
<!--<xsd:documentation>-->
<!--Modifications of these items are to be ignored.-->
<!--EXPERIMENTAL-->
<!--</xsd:documentation>-->
<!--<xsd:appinfo>-->
<!--<a:experimental>true</a:experimental>-->
<!--<a:since>3.7</a:since>-->
<!--</xsd:appinfo>-->
<!--</xsd:annotation>-->
<!--</xsd:element>-->
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="modificationPolicyConstraint" type="tns:ModificationPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="AssignmentModificationPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Constraint that triggers the rule when the object is assigned.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.5</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:ModificationPolicyConstraintType">
<xsd:sequence>
<xsd:element name="relation" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
This constraint only applies to relations of the specified type. The value
of this element is compared to the relation of the targetRef relation
in the assignment. If not specified then this policy only
applies to the null (default) relation. If all relations need to be
affected by this policy then the special value of "any" should be specified
in this element.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>AssignmentModificationPolicyConstraintType.relation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!--<xsd:element name="targetType" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">-->
<!--<xsd:annotation>-->
<!--<xsd:documentation>-->
<!--This policy only applies to targets of the specified type.-->
<!--</xsd:documentation>-->
<!--<xsd:appinfo>-->
<!--<a:since>3.6</a:since>-->
<!--</xsd:appinfo>-->
<!--</xsd:annotation>-->
<!--</xsd:element>-->
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="assignmentModificationPolicyConstraint" type="tns:AssignmentModificationPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="HasAssignmentPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
Constraint that triggers when the focus has given assignment(s).
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="targetRef" type="c:ObjectReferenceType">
<xsd:annotation>
<xsd:documentation>
Assignment target to be matched. Might be dynamic (with a resolution time of "run"), just
like the one in exclusion constraint. If a relation here is specified, it takes precedence
over "relation" item in this constraint.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>HasAssignmentPolicyConstraintType.targetRef</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="direct" type="xsd:boolean" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
If true the assignment to given target must be direct. If false, it must be indirect (induced).
If not specified, it might be either direct or indirect. But in all cases it must be of the order
one, i.e. metaroles are not considered.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>HasAssignmentPolicyConstraintType.direct</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="enabled" type="xsd:boolean" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
If true the assignment to given target must be effectively enabled. If false, it must be present
but effectively disabled (beware, the behavior of midPoint for disabled indirect assignments may
be fragile). If not specified, the effective status is not considered.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>HasAssignmentPolicyConstraintType.enabled</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="relation" type="xsd:QName" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
This policy only applies to relations of the specified type. (Provided that the relation
is not set in the targetRef.) The value of this element is compared to the relation of the
targetRef relation in the assignment/inducement. If not specified then this policy only
applies to the null (default) relation. If all relations need to be affected by this policy
then the special value of "any" should be specified in this element or in the targetRef element.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>HasAssignmentPolicyConstraintType.relation</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="hasAssignmentPolicyConstraint" type="tns:HasAssignmentPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:element name="hasNoAssignmentPolicyConstraint" type="tns:HasAssignmentPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="TimeValidityPolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
A constraint that triggers when validity of an object, assignment, or basically any time-sensitive
item (e.g. password) is about to end.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.6</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="item" type="t:ItemPathType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The item whose validity is to be checked. If not specified, activation/validTo is assumed.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>TimeValidityPolicyConstraintType.item</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignment" type="xsd:boolean" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
If set to true, validity of assignments of the relevant object are to be checked, not
items of the object itself. So, for example, if you want to send notifications before validity of
assignments to roles A, B, C expire, you'd need to attach a policy rule with this constraint
having assignment=true to roles A, B, and C.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>TimeValidityPolicyConstraintType.assignment</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="activateOn" type="xsd:duration" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
When will this policy constraint activate (trigger)? If not specified, activation will occur
on the moment of validity change. Specify negative durations if you need to activate the trigger
before that moment; and positive ones if the trigger should be activated after that.
</xsd:documentation>
<xsd:appinfo>
<a:displayName>TimeValidityPolicyConstraintType.activateOn</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="deactivateOn" type="xsd:duration" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
When will be this policy constraint deactivated? If not specified, it will be active forever.
Specify negative durations if you need to activate the trigger before the moment of validity
change; and positive ones is the trigger should be deactivated after that.
If not specified, the trigger will be active forever (TODO ok? or only until validTo occurs?)
</xsd:documentation>
<xsd:appinfo>
<a:displayName>TimeValidityPolicyConstraintType.deactivateOn</a:displayName>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="timeValidityPolicyConstraint" type="tns:TimeValidityPolicyConstraintType" substitutionGroup="tns:abstractPolicyConstraint" />
<xsd:complexType name="StatePolicyConstraintType">
<xsd:annotation>
<xsd:documentation>
A constraint that triggers when a object or assignment is in a given state.
If both filter and expressions are specified, both must be true in order for constraint to be triggered.
</xsd:documentation>
<xsd:appinfo>
<a:container/>
<a:since>3.7</a:since>
<a:experimental>true</a:experimental>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="tns:AbstractPolicyConstraintType">
<xsd:sequence>
<xsd:element name="filter" type="q:SearchFilterType" minOccurs="0">