Firstyear
Firstyear
I think this is actually achieved by #1122 and setting a default policy on idm_all_accounts.
@yaleman Do you think this is worth? I think we are moving away from pw's, and we try not to let people set bad passwords anyway, I'm also not sure...
It actually looks like this was done in 8a2f3b65ec so I think we can close this.
I think this could add a bit of complexity to the config parser. We wouldn't want people to have to change their configs to match this, and plenty of config...
Oh true. That's really true.
https://github.com/BurntSushi/memchr/tree/ce7b8e606410f6c81a63f45abb24c5b5aab5d741
@wrenix We actually removed all references to sql in our docs because this is a misnomer. You *can not* and *will never* be able to swap sqlite with another backend....
> For what matters SQLite is actually very performant at what it does. Kanidm can scale horizontally, as long as you only need one write replica (otherwise you could end...
> @Firstyear hmm, okay, so kanidm would never be scaleable? :( https://kanidm.github.io/kanidm/stable/repl/index.html
I think to achieve this we need to add a language-tagged string to the DB. This ties into #211 which supports this, as well as #2105 where we may wish...