GitLab

Prevents duplicate insertion of storageEncryptedSecretKey when
requesting an account recovery with opportunistic encryption enabled.

Add an integration test to cover this scenario.

There's no reason for it to be exposed, it is currently an
implementation detail in how new MySQL databases are created (the
password reset flow for databases does not use it after that).

Currently only usable to set the user status. Currently the status
changes are not propagated to owned resources.

Add a couple of interfaces to run arbitrary (including non-LDAP)
queries to discover a user's Resources.

The first implementation (beyond the previous behavior using a
statically templated LDAP query) is the mailing list discoverer, which
can find lists owned by an email alias, thus fixing issue #8.

32 random characters.

Add a test to verify at least the create/retrieve workflow.

We should run the integration tests when building the package.

Fixes issue #7.

Add tests to verify this is enforced.

Cache

See merge request !5

It will cache User objects (not directly the resources yet), wrapping
another Backend object and invalidating the cache on every
state-changing API call.

Add a section on configuration.

Create "better" JSON, rather than just dumping binary strings in it.

Avoid implementing our own version of asp/userenckey/u2f serialization
and deserialization.

Search

Closes #6

See merge request !4

To support pattern searches, make the LDAP query templates understand
both "admin-provided input" and "user-provided input", so that
wildcards will only be escaped in the latter case.