| Age | Commit message (Collapse) | Author |
|---|
|
merge. with @thaissiqueira.""
This reverts commit 1e6e165a3fc397e45884eaec1122ba0cc5ff923e.
|
|
|
|
|
|
This is the case of the infamous 'Unhandled error in Deferred' events
that were not logging the traceback.
|
|
I was surprised this test was not working correctly.
|
|
|
|
the old events if they were not cleaned up after previous errors
|
|
|
|
|
|
with @tayanefernandes
|
|
We were trying to setup services even after closing the session. We fixed it
and added unit test.
Related with: #815
|
|
When the upload of the user key fails (i.e. Timeout), the session was being held
in memory, preventing the user from trying again.
Related with: #815, #889
|
|
with @thaissiqueira."
This reverts commit ebdeec4ad6d0f91bc60fd34a580fc02787026692.
|
|
@thaissiqueira.
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
This was storing loglines and references of the objects until a
beginLoginTo was called. We moved to the new logger and added the
beginLoginTo line.
|
|
|
|
|
|
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
|
|
In case a user was being logged out and there's a soledad invalid
auth token error, there might be an inconsistent state where the
user session doesn't exist when this second logout is tried.
This was breaking the login for that user until the next UA restart,
I adapted the code to make logging out an user idempotent to
prevent this corner case
|
|
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
|
|
In some cases, the default home was not expanding
the user part of the path and was causing errors,
now we make sure the path is expanded when setting
the default value
|
|
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
|
|
|
|
services sessions
|
|
|
|
The previous description were mentioning dispatcher use, but since we
don't use it anymore, they were changed to refer to server-mode.
|
|
|
|
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
|
