AIUS/Overleaf
1
0
Fork 0
mirror of https://git.unistra.fr/aius/root/ldap-overleaf-sl.git synced 2024-10-05 23:23:59 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
sym 2023-11-21 12:20:20 +01:00 committed by GitHub
parent d049e4534a
commit c5e8e6f79a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -7,7 +7,7 @@ edition. Currently this repo uses sharelatex:latest.
The inital idea for this implementation was taken from The inital idea for this implementation was taken from
[worksasintended](https://github.com/worksasintended). [worksasintended](https://github.com/worksasintended).
# BREAKING CHANGE ## BREAKING CHANGE
be careful if you try to migrate from 3.3.2! Backup your machines and data. be careful if you try to migrate from 3.3.2! Backup your machines and data.
The migration paths hould be: The migration paths hould be:
- Backup Your machines and Data - Backup Your machines and Data
@ -15,7 +15,7 @@ The migration paths hould be:
- run this sharelatex image (4.1.1) and run the migrations scripts - run this sharelatex image (4.1.1) and run the migrations scripts
### Limitations: ## Limitations:
NEW: This version provides the possibility to use a separate ldap bind user. It does this just to find the proper BIND DN and record for the provided email, so it is possible that users from different groups / OUs can login. NEW: This version provides the possibility to use a separate ldap bind user. It does this just to find the proper BIND DN and record for the provided email, so it is possible that users from different groups / OUs can login.
Afterwards it tries to bind to the ldap (using ldapts) with the user DN and credentials of the user which tries to login. No hassle of password hashing for LDAP pwds! Afterwards it tries to bind to the ldap (using ldapts) with the user DN and credentials of the user which tries to login. No hassle of password hashing for LDAP pwds!