mart-w/kanidm
1
0
Fork 0
mirror of https://github.com/kanidm/kanidm.git synced 2025-02-23 12:37:00 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify role of WebUI in README.md (#2431)

Browse source 
* Clarify role of WebUI in README.md

---------

Co-authored-by: James Hodgkinson <james@terminaloutcomes.com>
This commit is contained in:
krumelmonster 2024-01-19 02:51:01 +01:00 committed by GitHub
parent e02e0501eb
commit 6c1950aa7b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -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
</details>
@ -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.