- 24 Jul, 2019 1 commit
-
-
putro authored
-
- 30 Jun, 2019 1 commit
-
-
ale authored
-
- 29 Jun, 2019 2 commits
- 23 Jun, 2019 2 commits
- 21 Jun, 2019 1 commit
-
-
ale authored
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).
-
- 13 Jun, 2019 1 commit
-
-
ale authored
-
- 10 Jun, 2019 1 commit
-
-
ale authored
-
- 09 Jun, 2019 5 commits
-
-
ale authored
Currently only usable to set the user status. Currently the status changes are not propagated to owned resources.
-
ale authored
-
ale authored
-
ale authored
-
ale authored
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.
-
- 25 May, 2019 1 commit
-
-
ale authored
32 random characters.
-
- 24 May, 2019 1 commit
-
-
ale authored
Add a test to verify at least the create/retrieve workflow.
-
- 05 May, 2019 9 commits
-
-
ale authored
Add tests to verify this is enforced.
-
ale authored
-
ale authored
-
ale authored
It will cache User objects (not directly the resources yet), wrapping another Backend object and invalidating the cache on every state-changing API call.
-
ale authored
-
ale authored
-
ale authored
Add a section on configuration.
- 03 Apr, 2019 1 commit
-
-
ale authored
-
- 27 Mar, 2019 1 commit
-
-
ale authored
-
- 21 Mar, 2019 2 commits
- 20 Mar, 2019 1 commit
-
-
ale authored
-
- 17 Feb, 2019 1 commit
-
-
ale authored
-
- 09 Feb, 2019 1 commit
-
-
ale authored
-
- 03 Feb, 2019 3 commits
- 14 Dec, 2018 2 commits
- 20 Nov, 2018 1 commit
-
-
ale authored
-
- 18 Nov, 2018 2 commits