Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typo fix #13

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

typo fix #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c99ab24
typo fix
catmug Oct 27, 2023
159a2af
typo fix
catmug Oct 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions midpoint/architecture/concepts/abstract-role.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
:page-wiki-metadata-modify-date: 2019-01-31T12:10:27.587+01:00

In midPoint parlance, _abstract role_ means any type of object that acts as a role.
This means that abstract tole can be used to give privileges to other objects.
This means that abstract role can be used to give privileges to other objects.
Following object types are abstract roles in midPoint:

* Role (`RoleType`)
Expand All @@ -28,4 +28,4 @@ In simple technical terms _abstract role_ means that the object may contain xref

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

* xref:/midpoint/reference/org/organizational-structure/[Organizational Structure]
* xref:/midpoint/reference/org/organizational-structure/[Organizational Structure]
4 changes: 2 additions & 2 deletions midpoint/reference/roles-policies/rbac/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ midPoint is using a (very) extended version of Role-Based Access Control (RBAC)
RBAC is originally defined as mostly static structure of users and roles.
The original RBAC defines that user assigned to the role gets all the rights implied by the role.
If two users have the same role, they have the same privileges.
However, this leads to the problem of xref:/iam/role-explosion/[role rxplosion] and numerous role maintenance problems.
However, this leads to the problem of xref:/iam/role-explosion/[role explosion] and numerous role maintenance problems.
We mitigate such problems by enhancing RBAC model with logic.
We extended basic RBAC model with ability to specify expressions in role definitions that determine how and when the role is used.
Therefore, the role can adapt to the attributes of user that has the role or even the role assignment itself can be parametrized.
Expand Down Expand Up @@ -154,4 +154,4 @@ See xref:/midpoint/reference/roles-policies/roles-and-policies-configuration/[Ro

* xref:/midpoint/reference/roles-policies/assignment/[Assignment]

* xref:/midpoint/reference/expressions/[Mappings and Expressions]
* xref:/midpoint/reference/expressions/[Mappings and Expressions]