Age | Commit message (Collapse) | Author |
|
Issue #684
|
|
|
|
using the cache
Issue #773
|
|
In order to replace leap_auth with bonafide, we created a
class to hold the user credentials
|
|
|
|
|
|
If we get any problem with the upload of the user's public key,
we are deleting the key pair from the local database and denying
login. That way, a new login will have a chance to regenerate the
key and upload it properly.
|
|
We covered a lot of missing cases on the keymanager tests. We also
isolated these tests, that caused some other tests to break, so we
fixed them.
|
|
|
|
|
|
I added a new test to check that an existing public key is not being
sent to leap on every login
|
|
Since we are creating the combined certificates at the beginning
of the UA and using it for multiple users, it makes more sense to
create it in the leap folder instead of on a temporary file
This bundle will be updated on every UA start
|
|
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
|
|
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
|
|
|
|
|
|
handling during multi-user boostrap
- reactor.stop will not work if the reactor is not running. This will make sure it will be stopped on bootstrap errors now.
- added a wrapper that returns a defer.fail for exceptions thrown during the multi-user boostrap
- Issue #535
|
|
Some keymanager api was updated, so we needed to update some calls.
|
|
Return 503 code while RootResource is in MODE_STARTUP
|
|
|
|
Issue 695: Show all recipients in mail sent folder
|
|
|
|
|
|
- now username and user_id are mapped when the user logs in
- Issue #686
|
|
register sends it too.
Issue #686
|
|
|
|
|
|
the reactor if single-user mode
Issue #689
|
|
|
|
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.
|
|
handles login, logout, mail and tags resources
|
|
|
|
|
|
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
|
|
|
|
- Deferred was not handled as required
- Test did not assert call to expire
|
|
- The main identifier of a key now is the fingerprint, not the id
anymore
- The address is not required anymore when creating the json
|
|
|
|
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
|
|
- Issue #615
- invalid token raised by soledad after timeout,
if we see this, recreate the session on next login
|
|
- Issue #615
- Fixed some long broken but not failing tests
|
|
For the case of wrong file path or file not existing
Issue #214
|
|
Instead shows a generic: "invalid xml format" message
Issue #214
|
|
|