From 6c1950aa7ba1f10b0831804780b88a9597cbb624 Mon Sep 17 00:00:00 2001 From: krumelmonster Date: Fri, 19 Jan 2024 02:51:01 +0100 Subject: [PATCH] Clarify role of WebUI in README.md (#2431) * Clarify role of WebUI in README.md --------- Co-authored-by: James Hodgkinson --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ad6a5f7c1..3301c3e7f 100644 --- a/README.md +++ b/README.md @@ -31,7 +31,7 @@ Kanidm supports: - RADIUS for network and VPN authentication - Read only LDAPS gateway for Legacy Systems - Complete CLI tooling for Administration -- User Self Service the WebUI +- A WebUI for User Self Service @@ -83,6 +83,9 @@ like Oauth2 and OIDC. To use these from LLDAP you need an external portal like K Kanidm they are "built in". However that is also a strength of LLDAP is that is offers "less" which may make it easier to administer and deploy for you. +While LLDAP offers a simple Web UI as the primary user management frontend, Kanidm currently only +offers administration functionality via its CLI. + If Kanidm is too complex for your needs, you should check out LLDAP as a smaller alternative. If you want a project which has a broader feature set out of the box, then Kanidm might be a better fit.