From 3828ec76246c98a228b93f76d9c895589d3f785f Mon Sep 17 00:00:00 2001 From: traverseda Date: Wed, 13 Nov 2024 07:38:45 -0400 Subject: [PATCH] example_configs: Update pam example for release 0.6..0 --- example_configs/pam/README.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/example_configs/pam/README.md b/example_configs/pam/README.md index 493cf13..695911b 100644 --- a/example_configs/pam/README.md +++ b/example_configs/pam/README.md @@ -1,7 +1,3 @@ -> [!IMPORTANT] -> The integration requires custom ldap properties which are not supported on -> stable (as of 2024-09-19), please use nightly/latest tag. - # Configure lldap You MUST use LDAPS. You MUST NOT use plain ldap. Even over a private network @@ -46,11 +42,6 @@ The provided implementation uses custom attributes to mark users and groups that should be included in the system (for instance, you don't want LDAP accounts of other services to have a matching unix user). -> [!TIP] -> You can create custom attributes in the Web UI, but to provide values, you -> need to communicate with the API, see [scripting]. Example using lldap-cli: -> `./lldap-cli user update set example-user unix-uid 5000` - For users, you need to add an (integer) `unix-uid` attribute to the schema, and manually set the value for the users you want to enable to login with PAM.