Skip to content

Commit

Permalink
Merge branch 'docs/cleanup-4.8'
Browse files Browse the repository at this point in the history
  • Loading branch information
semancik committed Dec 4, 2023
2 parents c41595a + f26d3b1 commit 0d186de
Showing 1 changed file with 13 additions and 2 deletions.
15 changes: 13 additions & 2 deletions docs/schema/archetypes/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -55,11 +55,22 @@ Following table lists commonly-used archetypes and their mapping to primary midP


| ServiceType
| Application, Device, Printer, Provider, Network, Web API endpoint
| Application, Device, Printer, Provider, Network, Web API endpoint, Robot


|===

== Birthrights

Archetypes are the primary tool to define a glossref:birthright[birthright provisioning].
Archetypes behave as xref:../roles-policies/rbac/[roles].
Therefore, any privileges specified in archetype xref:/midpoint/reference/roles-policies/assignment/assignment-vs-inducement/[inducements] are automatically applied to all the objects that have the archetype.
This approach can be used to apply _birthright_ to the objects, e.g. it can specify baseline privileges for all employees or students.

Moreover, archetypes may work as xref:/midpoint/reference/roles-policies/metaroles/policy/[metaroles], specifying common behavior for object types.
For example, `Project` archetypes may specify common behavior for all projects, including baseline authorization for project members and managers.
Overall, archetypes provide very flexible and powerful mechanism to specify _birthrights_.

== Archetype Definition

Archetype definition is a special midPoint object (ArchetypeType).
Expand Down Expand Up @@ -149,4 +160,4 @@ See xref:/midpoint/features/planned/archetypes/[Archetype Improvements (Planned

* xref:/midpoint/reference/roles-policies/rbac/[Advanced Hybrid RBAC]

* xref:/midpoint/reference/misc/services/[Services]
* xref:/midpoint/reference/misc/services/[Services]

0 comments on commit 0d186de

Please sign in to comment.