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 16 Packages Projects Releases Wiki Activity

Update readme

Browse source
This commit is contained in:
William Brown 2021-02-18 09:28:36 +10:00
parent 483aa6f23d
commit 06e3c24704
1 changed files with 25 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
README.md
View file

@ -38,26 +38,39 @@ answer questions via email, which can be found on their github profile.
[gitter community channel]: https://gitter.im/kanidm/community [gitter community channel]: https://gitter.im/kanidm/community
## Implemented/Planned features ## Features
* SSH key distribution for servers (done) ### Implemented
* Pam/nsswitch clients (with limited offline auth) (done)
* Sudo rule distribution via nsswitch * SSH key distribution for servers
* CLI and WebUI for administration * Pam/nsswitch clients (with limited offline auth)
* OIDC/Oauth * MFA - TOTP
* Highly concurrent design (MVCC, COW)
* RADIUS integration
### Currently Working On
* CLI for administration
* MFA - Webauthn
### Upcoming Focus Areas
* WebUI for self service with wifi enrollment, claim management and more.
* RBAC/Claims (limited by time and credential scope) * RBAC/Claims (limited by time and credential scope)
* MFA (Webauthn, TOTP) (TOTP done) * OIDC/Oauth
* Highly concurrent design (MVCC, COW) (done)
* Replication (async multiple active write servers, read only servers) * Replication (async multiple active write servers, read only servers)
### Future
* Sudo rule distribution via nsswitch
* WebUI for administration
* Account impersonation * Account impersonation
* RADIUS integration (done)
* Self service UI with wifi enrollment, claim management and more.
* Synchronisation to other IDM services * Synchronisation to other IDM services
## Features we want to avoid ### Features We Want to Avoid
* Auditing: This is better solved by SIEM software, so we should generate data they can consume. * Auditing: This is better solved by SIEM software, so we should generate data they can consume.
* Fully synchronous behaviour: This is slow. * Fully synchronous behaviour: This prevents scaling and our future ability to expand.
* Generic database: We don't want to be another NoSQL database, we want to be an IDM solution. * Generic database: We don't want to be another NoSQL database, we want to be an IDM solution.
* Being LDAP/GSSAPI/Kerberos: These are all legacy protocols that are hard to use and confine our thinking - we should avoid "being like them". * Being LDAP/GSSAPI/Kerberos: These are all legacy protocols that are hard to use and confine our thinking - we should avoid "being like them".