| c6df1d605fb3e235df6d4a21ae00632c9d6e3cc2 |
|
19-Jul-2011 |
Marc Blank <mblank@google.com> |
Prevent NPE's in AccountSecurity
* This CL fixes the referenced bug, but it does NOT explain how
mAccount; best guess is that the process was killed and then
restarted when the result from DPM was available.
* Assuming this is the case, we remove the background task loading
mAccount, avoiding a possible race.
* Also, it's not clear why clearNotifications didn't use the
account id argument; what if there's more than one account that
uses security? Filing a bug about this.
Bug: 5048912
Change-Id: I734834337ab6e409d77624e7c7370350de76becb
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| e2d28a06077ac0c394f1989b97a9f8d0019daa01 |
|
18-Jul-2011 |
Marc Blank <mblank@google.com> |
Clear "security needed" notification when releasing holds
* This fixes the issues with erroneous notifications remaining
active
Bug: 5039388
Change-Id: Ib1cd506e732e34f6368036a131d79270b22d4a4b
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| bc2eaadde987044027b57d241e635de014bdb8ba |
|
01-Jul-2011 |
Makoto Onuki <omakoto@google.com> |
Use parallel executor
We should eventually replace all with EmailAsyncTask, but it's the safest thing
we can do now to avoid regression.
Change-Id: I78bfc4fb2be1dcfadeb7f90092ec7adb35c1d393
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| d09cff08882e553afce919865a2cc60b657d4659 |
|
06-May-2011 |
Ben Komalo <benkomalo@google.com> |
Make "don't allow camera" a supported policy.
This sends the bit to the DPM. Separate changes have been/will be made
to change the provision parser and support it in the DPM.
Bug: 4185316
Change-Id: I44872ceb095a28539b047a0641cc499c7186a9b3
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| f5418f1f93b02e7fab9f15eb201800b65510998e |
|
14-Jun-2011 |
Marc Blank <mblank@google.com> |
Move Account into its own top-level class
Change-Id: Ide7c991b7d4d418dbe17164421425bf898ba64ee
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 12b82d9374947c9268217f45befe8a74bd9b60d7 |
|
20-May-2011 |
Ben Komalo <benkomalo@google.com> |
Move HostAuth to top level class.
No other changes made.
Change-Id: I1c6497c98abc0f99443ea42d8aed6295b263c123
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| aeee10e57ef4d931e7708fde218d590453a82aea |
|
28-Apr-2011 |
Marc Blank <mblank@google.com> |
Rework of security policy storage
* Replace crazy (and soon to be "full") bit fields stored in an account's
securityFlags with a row in a newly created Policy table (thus, fully
expandable)
* Update code from database version 17 to 18; adds Policy table, a
policyKey row in Account, and a revised trigger that deletes Policy
information for deleted Accounts
* Update old PolicySet unit tests to work against the new Policy class
* Add test for the conversion of securityFlags to Policy
* Tested in a variety of scenarios; appears to be functionally equivalent
Change-Id: I1505ee75230d6a0d3c2b62a46326f39c2c7f9eb5
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| f4894131427ec7562fcb05388b9f3aa094e388bc |
|
19-Feb-2011 |
Andy Stadler <stadler@google.com> |
Add contextual dialogs after notifications
* When security settings notification is clicked, inform user that
they need to change settings (before dumping them in security
settings.)
* On an authentication failure, present a dialog to the user explaining
that the username or password may be incorrect.
* When the device pin/password is expiring or expired, present a dialog
to the user explaining that it needs to be updated.
Bug: 3238657
Change-Id: I8fca446fa3c1bf87a95938553dbdc362c3df220e
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 31d9acbf0623872f9d4a2b3210b5970854b654c7 |
|
12-Feb-2011 |
Marc Blank <mblank@google.com> |
Email split, part huit: Refactor constants, clean emailcommon
* There are three pieces to this CL (sorry):
1) Move and/or rename some constants into emailcommon
2) Move Utility to emailcommon, moving the few UI
related utilities back into Email (FolderProperties
and UiUtilities)
3) Remove all references to resources from emailcommon
* The three pieces relate in that, between them, they allow
the emailcommon static library to compile cleanly
Bug: 3442973
Change-Id: Ic5e3abaa2a1b36999e0b6653c6c2134ea1bd544f
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| a7bc0319a75184ad706bb35c049af107ac3688e6 |
|
10-Feb-2011 |
Marc Blank <mblank@google.com> |
Email split, part six: EmailContent
* Moved EmailContent to emailcommon
Change-Id: Ib3db1bfcfe74554c0e5afd3cfce6d72f26e9aeb9
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 45bfac00e58059eed71fd22e2767c8e0437b6251 |
|
24-Jan-2011 |
Andy Stadler <stadler@google.com> |
Rework account security bootstrap procedure
* Bug to fix was that it was looping if the user canceled
password or encryption setup (instead of simply re-notifying.)
* Solution was to refactor all code into a single sequence of checks,
rerun the sequence each time, and set markers to prevent looping.
* Rework needed after the changes in I54f39bc9 which added
encryption support but introduced the looping behavior.
* Removed a UI-thread DB access
Bug: 3346641
Change-Id: I0791d7a16287efecc7121b5ffa0db26ca2b05151
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 469f2987dc11d153434e50eb04dd6b83b924d09d |
|
13-Jan-2011 |
Andy Stadler <stadler@google.com> |
Add encryption to SecurityPolicy
* Add encrypted-storage to uses-policies
* Add new field to PolicySet
* Add "false" to all constructor callers
* Add unit tests (including fixing some existing unit tests)
* Add new logic to AccountSecurity activity t0 dispatch both password
and encryption requests.
Bug: 3346641
Change-Id: I54f39bc9b6fbe21c033a05b36b83081e5c78a296
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| cd09545b87979fa6b4337f17b5a001f0ef7b5269 |
|
02-Nov-2010 |
Andrew Stadler <stadler@android.com> |
Provide runtime switch for GL acceleration
* new checkbox in debug fragment
* saved value in prefs so it's sticky
* each Activity calls a helper to enable/disable per that flag
Change-Id: I1af1ae9f401bc746cc97da00dfb0e06407b79d46
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| d22651ccd14939dc287cb32bf5403f5bb51aaeac |
|
29-Sep-2010 |
Andy Stadler <stadler@android.com> |
am 060b1df0: am a9bc41f5: Show server name instead of account name
Merge commit '060b1df06954be1d72a659b0f00e30b8057484e0'
* commit '060b1df06954be1d72a659b0f00e30b8057484e0':
Show server name instead of account name
|
| a9bc41f5ecea991d06b88ce861a412288303e9dd |
|
29-Sep-2010 |
Andy Stadler <stadler@android.com> |
Show server name instead of account name
The format string "The server %s requires that you allow it to remotely
control some security features of your phone." was being displayed with
the account name instead of the server name.
Bug: 3011124
Change-Id: I1aadb5790297777831dd69f04ea89641240b7b87
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| bcf32320e2600e96c8a9e997a8903bfc3893b35e |
|
27-Jul-2010 |
Makoto Onuki <omakoto@google.com> |
Move isSecurityHold/clearAccountHoldFlags to Account
- Added unit tests
- I see the "open a cursor, move to the first row, read a column" pattern over
and over. Added a utility method for this. (Let's try not to bloat the
binary by copying code around!)
- Added helper classes for database related tests
- Removed code dup
Change-Id: I380959215cc1661b252158f0f6e35369b499cdf8
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| a87f8d8bbc0b704974c4230f518cf23b7215fc55 |
|
13-Apr-2010 |
Andrew Stadler <stadler@android.com> |
Changes to improve security policy setup
* SecurityPolicy: Fix bug that prevents any notifications after the
user hits "cancel all" from the notification pane.
* AccountSecurity: If the user cancels the device admin acceptance
activity, repost the notification.
* MesageList: Catch security hold condition when entering a mailbox, and
launch security setup activity.
Bug: 2585159
Change-Id: I60d5d8c693cc5f00fe98a9cc69265802f5bee813
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 6d0016229adc13fefe68820fe4d6e46f530952ba |
|
27-Feb-2010 |
Dianne Hackborn <hackbod@google.com> |
Move DeviceAdmin APIs to android.app.admin.
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| d71d0b223a5cd02e2a8f1ec5c3f8cebab170d65f |
|
10-Feb-2010 |
Andrew Stadler <stadler@android.com> |
Force security activation after new account create
On new accounts, we can accelerate the process of setting up security
by explicitly checking (at the end of the security process). The user
is not required to "answer" the asynchronous notification.
This is an imperfect solution, as a slow initial sync could leave the
user in a non-synced Inbox (with a notification waiting for them), but
we can come back to this after we evaluate real-world performance.
Bug: 2387961
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 2a5eeea9213005060256054ec773e72406415ce4 |
|
09-Feb-2010 |
Andrew Stadler <stadler@android.com> |
Adding security hold flag to accounts
* Add hold flag to Account flags
* Add code to set it (when EAS reports policy failure)
* Add code to clear it when we see changes from the device admin side
* unit tests
This should be sufficient to restart sync of an account which is on hold
due to security policy requirements. Note, this is considered a "retry",
and if the account still does not meet requirements for some reason, it
is expected that EAS sync will call policiesRequired() again.
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|
| 3d2b3b3b3554be2ac23d9a49fee00faa9693e857 |
|
05-Feb-2010 |
Andrew Stadler <stadler@android.com> |
Logic to move phone into security-admin mode
* Create notification to display when syncs fail due to security
* Create psuedo-activity (no UI) to manage device admin state transitions
* Clean up and flesh out SecurityPolicy APIs'
* Add placeholders in EasSyncService showing how to react when policies
are not met and sync cannot continue.
Note: There are some STOPSHIP todo's at the top of SecurityPolicy.java.
These should explain any code that you might think is "missing".
/packages/apps/Email/src/com/android/email/activity/setup/AccountSecurity.java
|