Document new authentication (including SQLite support)

[AlekSi]

What should be done?

We should document our new experimentation authentication support, including setup flags.

Where?

Docs.

Definition of Done

• Documentation updated.

[muety]

Am I right in understanding that currently there is no way to do authentication with SQLite whatsoever? That is, when creating two separate databases for two different applications, there is no way of preventing one app from accessing the other's data?

[AlekSi]

Correct. Currently, FerretDB does not store authentication or authorization information for any backend. For PostgreSQL, we use PostgreSQL's usernames and passwords: https://docs.ferretdb.io/security/authentication/. In SQLite, we don't even have that yet.

There are roughly two options to solve that issue. One is to use the user-auth SQLite extension mentioned in the description. Another is to do #7 and store authentication information ourselves.

[muety]

Second option sounds harder, but also more sensible, because would give us (a) SQLite authentication and (b) a couple more supported commands in addition. Looking forward to having this! Missing SQLite authentication is the only thing that currently keeps me from switching to Ferret for my apps.

[AlekSi]

v1.22 support authentication for SQLite via a new experimental flag: https://blog.ferretdb.io/new-ferretdb-v122-user-setup-feature/
What's left is community testing and documentation.

[Fashander]

I'm picking this up. Mainly, we need to update the documentation for these pages:

• https://docs.ferretdb.io/security/authentication/
• https://docs.ferretdb.io/quickstart-guide/docker/ (SQLite authentication now available via experimental new flag)

[AlekSi]

It will be out in 1.24 later today!