From 871c622ec5cc8029c25532e618e234c12ce09fea Mon Sep 17 00:00:00 2001 From: ebner Date: Wed, 17 Jun 2026 14:50:57 +0200 Subject: [PATCH] fix issues --- .../admin-guide/configuration/basic/ad_integration.md | 11 +++++------ docs/admin-guide/virtual_machines.md | 4 ++-- docs/engineering-guide/accounts-and-groups.md | 7 ++----- 3 files changed, 9 insertions(+), 13 deletions(-) diff --git a/docs/admin-guide/configuration/basic/ad_integration.md b/docs/admin-guide/configuration/basic/ad_integration.md index 966f81ae..2a04c8f9 100644 --- a/docs/admin-guide/configuration/basic/ad_integration.md +++ b/docs/admin-guide/configuration/basic/ad_integration.md @@ -40,7 +40,7 @@ If AD changes should be reflected rather soonish, then change to aaa::sssd_cache_timeout: 300 ``` but please do not lower the renewal interwal to such values as it causes quite some constant traffic and load to the AD and the node itself. The renewal value is not applied if it is bigger than the timeout. You may also explicitely disable it with -``` +```yaml aaa::sssd_cache_renewal_interval: null ``` @@ -51,17 +51,16 @@ It is possible to connect the authentication daemon `sssd` using a generic `LDAP We suggest to use primarily the `AD` provider. It will show all AD users. - -Only where [eaccounts] (../access/eaccounts) are used with network home for eaccounts and local homes for the other users, then there must the `LDAP` provider configured. +Only where **eaccounts** are used with network home for eaccounts and local homes for the other users, then there must the `LDAP` provider configured. The `AD` provider (default on RHEL9+) is selected with -``` +```yaml aaa::sssd_ad_provider: true ``` The `LDAP` provider is selected with -``` +```yaml aaa::sssd_ad_provider: false ``` @@ -69,6 +68,6 @@ aaa::sssd_ad_provider: false You may opt out in Hiera with -``` +```yaml aaa::enable_ad: false ``` diff --git a/docs/admin-guide/virtual_machines.md b/docs/admin-guide/virtual_machines.md index 06ba1802..f34f34cc 100644 --- a/docs/admin-guide/virtual_machines.md +++ b/docs/admin-guide/virtual_machines.md @@ -9,8 +9,8 @@ Please provide at least following information with the request: - Hostname of virtual server - OS (Linux / Windows) - Number of CPUs -- Memory [GB] -- Diskspace [GB] +- Memory \[GB] +- Diskspace \[GB] If you can give more details to your plans the better! You may need to pay for the VM in certain cases. This will be determined in the process. diff --git a/docs/engineering-guide/accounts-and-groups.md b/docs/engineering-guide/accounts-and-groups.md index 86ef3317..b4d7ee9e 100644 --- a/docs/engineering-guide/accounts-and-groups.md +++ b/docs/engineering-guide/accounts-and-groups.md @@ -156,14 +156,11 @@ A number of groups have very low GIDs (\<500), in particular: ### `linux_ldap`: query LDAP -The [linux_ldap]{.title-ref} account has read-only permissions on a -limited subset of the LDAP attributes. It is used by -[nslcd]{.title-ref}, for example, to query LDAP for users\' uid, gid, -etc. +The **linux_ldap** account has read-only permissions on a limited subset of the LDAP attributes. It is used by `nslcd`, for example, to query LDAP for users' uid, gid, etc. The password should not be shared unnecessarily, but it does not need to be specifically protected either. In fact, in earlier releases of -Scientific Linux it was necessary to have [/etc/nslcd.conf]{.title-ref}, +Scientific Linux it was necessary to have `/etc/nslcd.conf`, which contains the password, world-readable. This account **must not** be given additional access or privileges.