Enabled password hashing for LDAP and Keycloak

This commit is contained in:
Kevin Veen-Birkenbach 2025-02-27 10:47:50 +01:00
parent 2b3cdd58d6
commit 3d096f1fc7
4 changed files with 18 additions and 8 deletions

View File

@ -253,11 +253,4 @@
roles:
- role: nginx-redirect-www
# Helper Roles for partial deployment
- name: Copy global css
hosts: nginx-modifier-css
become: true
roles:
- role: nginx-modifier-css
- import_playbook: playbook.destructor.yml

View File

@ -2044,7 +2044,7 @@
"always"
],
"usePasswordModifyExtendedOp": [
"false"
"true"
],
"trustEmail": [
"false"

View File

@ -0,0 +1,6 @@
# Activates Password hashing in ldap
dn: cn=config
changetype: modify
replace: olcPasswordHash
olcPasswordHash: {SSHA}

View File

@ -99,6 +99,11 @@ docker-compose exec -it -u www-data application /var/www/html/occ
docker compose exec -it -u www-data application php occ user:list
```
#### Sync Users
```bash
docker compose exec -it -u www-data application php occ user:sync
```
#### Create user via CLI
```bash
docker compose exec -it -u www-data application php occ user:add {{username}}
@ -161,6 +166,12 @@ More information: https://docs.nextcloud.com/server/latest/admin_manual/configur
SELECT * FROM `oc_appconfig` WHERE appid LIKE "%ldap%" and configkey != "s01ldap_agent_password";
```
## Update User with LDAP values
```bash
docker compose exec -it -u www-data application php occ ldap:check-user --update {{username}}
```
## Federation
If users are just created via Keycloak and not via LDAP, they have a different username. Due to this reaso concider to use LDAP to guaranty that the username is valid.