From 06112447d4d6922c1190be1927dfa047e198c3f5 Mon Sep 17 00:00:00 2001 From: Chris Hastie Date: Fri, 22 Jul 2016 21:03:46 +0100 Subject: [PATCH] Tidy README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1696eee..f150ab7 100644 --- a/README.md +++ b/README.md @@ -54,14 +54,14 @@ Troubleshooting About the user cache -------------------- -When a successful login is made against an LDAP server the plugin will cache the username and encrypted password. Currently this is done by saving them in an array in YOURLS options table. This has some advantages: +When a successful login is made against an LDAP server the plugin will cache the username and encrypted password. Currently this is done by saving them in an array in the YOURLS options table. This has some advantages: * It reduces requests to the LDAP server * It means that users can still log in even if the LDAP server is unreachable * It means that the YOURLS API can be used by LDAP users Unfortunately, the cache will not scale well. This is because it integrates tightly with YOURLS's internal auth mechanism, and that does not scale. If you have a few tens of LDAP users likely to use your YOURLS installation it should be fine. Much more than that and you may see performance issues. If so, you should probably disable the cache. This will mean -that your LDAP users will not be able to use the API. At least not unless they are listed in users/config.php, which suffers from the same scaling problems. +that your LDAP users will not be able to use the API. At least not unless they are also listed in users/config.php, which suffers from the same scaling problems. License -------