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
|
|
|
|
In order to replace leap_auth with bonafide, we created a
class to hold the user credentials
|
|
The login resource was being totally mocked out of the integration
tests, I adapted the test client to touch the actual login code
and fixed the multi_user_client to use the same checker the single
user one was using. With that change we now have tests that cover
the change of authenticating with bonafide
|
|
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
|
|
|
|
|
|
Issue #612
|
|
close soldedad and remove it from cache
Issue #586
|
|
Issue #590
|
|
Issue #583
|
|
Issue #583
|
|
Issue #576
|
|
- Issue #576
- Extended AppTestClient with multi user support
|
|
- Issue #576
- Step towards functional tests for multi user
|
|
Issue #576
|
|
Issue #576
|