mart-w/kanidm
1
0
Fork 0
mirror of https://github.com/kanidm/kanidm.git synced 2025-02-24 04:57:00 +01:00
Code Issues Actions 10 Packages Projects Releases Wiki Activity

Fix multiple typo in docs

Browse source
This commit is contained in:
Pando85 2020-04-25 10:43:16 +02:00 committed by Firstyear
parent 6c87cefca5
commit cfdaa702e5
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
kanidm_book/src/accounts_and_groups.md
View file

@ -81,7 +81,7 @@ An example can be easily shown with:
## Why Can't I Change admin With idm_admin? ## Why Can't I Change admin With idm_admin?
As a security mechanism there is a distiction between "accounts" and "high permission As a security mechanism there is a distinction between "accounts" and "high permission
accounts". This is to help prevent elevation attacks, where say a member of a accounts". This is to help prevent elevation attacks, where say a member of a
service desk could attempt to reset the password of idm_admin or admin, or even a member of service desk could attempt to reset the password of idm_admin or admin, or even a member of
HR or System Admin teams to move laterally. HR or System Admin teams to move laterally.
@ -102,7 +102,7 @@ Further, groups that are considered "idm_high_privilege" can NOT be managed
by the standard "idm_group_manage_priv" group. by the standard "idm_group_manage_priv" group.
Management of high privilege accounts and groups is granted through the Management of high privilege accounts and groups is granted through the
the "hp" variants of all privilieges. For example: the "hp" variants of all privileges. For example:
* idm_hp_account_read_priv * idm_hp_account_read_priv
* idm_hp_account_manage_priv * idm_hp_account_manage_priv

2
kanidm_book/src/posix_accounts.md
View file

@ -25,7 +25,7 @@ group id to the gid number of the UPG.
As there is now an equivalence between the uid and gid number of the user and the UPG, As there is now an equivalence between the uid and gid number of the user and the UPG,
there is no benefit to seperating these values. As a result kanidm accounts *only* there is no benefit to seperating these values. As a result kanidm accounts *only*
have a gidnumber, which is also considered to be it's uidnumber as well. This has a benefit have a gidnumber, which is also considered to be it's uidnumber as well. This has a benefit
of preventing accidental creation of a seperate group that has an overlapping gidnumber of preventing accidental creation of a separate group that has an overlapping gidnumber
(the uniqueness attribute of the schema will block the creation). (the uniqueness attribute of the schema will block the creation).
### UPG generation ### UPG generation

2
kanidmd/src/lib/constants/entries.rs
View file

@ -340,7 +340,7 @@ pub static JSON_DOMAIN_INFO_V1: &str = r#"{
} }
}"#; }"#;
// Anonymous should be the last opbject in the range here. // Anonymous should be the last object in the range here.
pub static JSON_ANONYMOUS_V1: &str = r#"{ pub static JSON_ANONYMOUS_V1: &str = r#"{
"attrs": { "attrs": {
"class": ["account", "object"], "class": ["account", "object"],