Age | Commit message (Collapse) | Author |
|
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 functional tests depend on a pre-existing default user. As it uses
the integration test client, we added this default user to the client
setup.
|
|
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
|
|
|
|
fixing build -- Issue #694
|
|
|
|
|
|
|
|
|
|
|
|
There is an update on leap_mail where an user id became required to
create an Account. So, this change update the Account usage on user
agent to pass this parameter.
|
|
Migrate all usage of leap.ImapAccount to leap.Account
We had to adapt some calls because of signature changes and, because
we need the Account to be initialized before moving on, we are directly
using the deferred initialization that the account has
See: https://github.com/leapcode/leap_mail/pull/228
|
|
xsrf cookies
-fixing functional test
Issue #612
|
|
Issue #612
|
|
- root resources changes the csrf token cookie everytime it is loaded, in particular during the intestitial load during login
- it will also add that cookie on single user mode
- initialize will still load all resources
- but they you cant access them if the csrf token do not match
- all ajax calls needs to add the token to the header
- non ajax get requests do not need xsrf token validation
- non ajax post will have to send the token in as a form input or in the content
Issue #612
|
|
Provide the proper content-type
Quote filename due to Firefox bug https://bugzilla.mozilla.org/show_bug.cgi?id=221028
|
|
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
|
|
- Issue #576
- To start in multi user, run with --multi-user --provider provider-name.tld
|
|
- Issue #576
|
|
now --
Issue #576
|
|
Issue #576
|
|
Issue #576
|
|
Issue #576
|
|
Issue #576
|
|
- Issue #576
- Only first step (other services not changed yet)
- Faked session access for now
|
|
- Issue #576
|
|
- Created the replier component to generate the reply dict for the
email. This was needed to decouple the InputMail from the need to know
who is the logged user.
|
|
|
|
including saving attachments.
Issue #548
|
|
|
|
don't use initialize method of root_resource in test
|
|
|
|
|
|
|
|
We removed Pixelated mail tests and adapted the remaining tests to use
Leap mail instead of it. Completely removed that now
|