| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
leap session creation is only done post-interstitial
and that logic is also extracted into its own class
#795
|
|
We also did some refactoring in order to have things working. #795
|
|
This is ongoing work to be able to accept and validate user domain
on login (so the user can use <username> or <username@domain.com>)
We are extracting the authentication logic from login_resource to be
able to test and cover the cases we need
|
|
|
|
|
|
using the cache
Issue #773
|
|
In order to replace leap_auth with bonafide, we created a
class to hold the user credentials
|
|
This still uses the SRPSession object to hold the credentials
so we don't have to adapt the rest of the user agent code
|
|
With this change we don't have to create the combined_ca_bundle
for every user at every login.
To support this change, we started migrating away from the
LeapCertificate class that was making the LeapProvider setup
more brittle
|
|
|
|
SMTP json is a blocking HTTP request that was taking ~1 sec
of the session creation. We moved it to the UA initialization
|
|
Soledad json must only be downloaded after we
fetch the api provider certificate, we can't
make the request for it before having this cert
|
|
Started adapting get_leap_session to deferreds
Soledad and keymanager setup calls will now
happen in deferreds and leap session creation
itself is a deferred with callbacks
This is a start in breaking the big blocking
calls we were doing on the main thread, this
was done without changing code inside the
leap libraries yet so things can be further
optimized
This breaks the ~4 seconds get_leap_session
piece into smaller 1 seconds one, that can be
further optimized and deferred to even smaller
calls
There are requests calls happening on the main
thread that should get this number even further
down
Also moved some pieces from bitmask libraries
to our bootstrap, because they are not bitmask
libraries anymore and that was causing confusion
|
|
Consolidated authentication to always be
done is a defer to thread and changed the
authenticate_user method name to conform
with what it actually does
|
|
Since we're not using dispatcher anymore, it doesn't make sense to keep
dispatcher references and program flows that depend on it. For example,
it doesn't make sense keep the flag --organization-mode, so it was
removed as well.
|
|
- Issue #615
- invalid token raised by soledad after timeout,
if we see this, recreate the session on next login
|
|
Issue #583
|
|
|
|
- Issue #576
|
|
- Issue #576
- To start in multi user, run with --multi-user --provider provider-name.tld
|
|
|
|
|
|
This reverts commit e3bdf2411dda9e25d87d7fb96da05a6ecfc624ee.
Issue fixed in the meantime, sorry.
|
|
pixelated-maintenance failed, presumably due to
0bf81341f33ac415d48c0b012fb66c8f7df45f57.
|
|
|
|
|
|
|
|
Changed logging level to WARN in order to prevent logging gpg keys.
|
|
Make a logic to add the welcome mail in INBOX when the user log into
account at the first time
|
|
- Issue #468
- Call with: pixelated-maintenance repair
|
|
Imap account creation was firing post sync hooks
and that was trying to use the mailboxes that were
not synced yet. Just moved that for the after sync
together with the incoming mail fetcher
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With this last change, it is now possible to run more than one user
agent on same pc without docker. With a fixed one it would raise port
already in use and it is not configurable, making it impossible to run
multiple activist UA.
|
|
|
|
That way we don't need extra logic for the welcome
mail, we just have to read the file and send the contents
to the input mail parser and that's it.
Also moved the logic of adding a welcome mail to the mailboxes
because it has knowledge of mailbox methods anyways.
|
