platform_packages_apps_KeyChain/tests/AndroidManifest.xml, branch master Unnamed repository; edit this file 'description' to name the repository. Inspect issuers when deciding on a certificate to display 2020-03-18T20:09:26+00:00 Eran Messeri eranm@google.com 2020-03-12T22:45:50+00:00 6f5ada6c4601a7d98eab79b789be8e450c462f4a To comply with RFC5246, KeyChain activity needs to inspect every certificate in the certificate chain of a client certificate, as the issuers list specified by the server could denote any certificate in the chain. Add a test to assert that specifying any issuer in the chain would cause the certificate to be marked presentable, and modify KeyChain to load and extract all issuers from the chain installed with the certificate. To get the test running, it's fixed to be a proper instrumentation test sharing the system UID so it can call code internal to the KeyChain package. Also fix broken service logging tests. Bug: 142043186 Test: atest KeyChainTests Change-Id: If03a71dcf0d8dc51f00f414c6aaad23b3ef2e952 
To comply with RFC5246, KeyChain activity needs to inspect every
certificate in the certificate chain of a client certificate,
as the issuers list specified by the server could denote any
certificate in the chain.

Add a test to assert that specifying any issuer in the chain would cause
the certificate to be marked presentable, and modify KeyChain to load
and extract all issuers from the chain installed with the certificate.

To get the test running, it's fixed to be a proper instrumentation test
sharing the system UID so it can call code internal to the KeyChain
package.

Also fix broken service logging tests.

Bug: 142043186
Test: atest KeyChainTests
Change-Id: If03a71dcf0d8dc51f00f414c6aaad23b3ef2e952
Adding modern KeyChain tests 2019-08-13T20:11:19+00:00 Eran Messeri eranm@google.com 2019-08-12T14:18:55+00:00 59a0d34cd1748abbfe1c5992c84c74e037f8993e The old KeyChain tests had to be manually run, which meant they never ran and were mostly broken. Add new, modern KeyChain tests that can be run with atest, as they are based on instrumentation tests. In particular: * Add BasicKeyChainServiceTest which currently includes one test case: importing a key and validating access to a key given a grant. * Removed mentioning of the KeyChainServiceTest as a service from the tests' AndroidManifest.xml because there's no reason this service should be bound anymore. * Adding AndroidTest.xml to describe the dependency between the support package and the tests: The KeyChainServiceSupport package must be installed alongside the test apk as this is a system package that is used to manipulate the KeyStore state directly. Its service is directly bound. * Overhaul the AndroidManifest.xml to indicate use of the instrumentation test runner. Bug: 138375478 Test: atest KeyChainTests Change-Id: If12251b40e5b089e2658788b008ce0a1be062a97 
The old KeyChain tests had to be manually run, which meant they never
ran and were mostly broken.

Add new, modern KeyChain tests that can be run with atest, as they are
based on instrumentation tests.

In particular:
* Add BasicKeyChainServiceTest which currently includes one test case:
  importing a key and validating access to a key given a grant.
* Removed mentioning of the KeyChainServiceTest as a service from the
  tests' AndroidManifest.xml because there's no reason this service
  should be bound anymore.
* Adding AndroidTest.xml to describe the dependency between the support
  package and the tests: The KeyChainServiceSupport package must be
  installed alongside the test apk as this is a system package that
  is used to manipulate the KeyStore state directly. Its service
  is directly bound.
* Overhaul the AndroidManifest.xml to indicate use of the instrumentation
  test runner.

Bug: 138375478
Test: atest KeyChainTests
Change-Id: If12251b40e5b089e2658788b008ce0a1be062a97
KeyChain testing: Fix KeyChainServiceTest 2017-11-03T13:48:11+00:00 Eran Messeri eranm@google.com 2017-11-01T10:54:10+00:00 43fb3695ddc259f12f1fc8b7b6fa13a04dcf2465 Since O, launching the KeyChainServiceTest in the background does not work since background execution is limited by default. Add instructions how to work around this for the test. Additionally, include the component in the intents to launch the support & keychain services, as Service Intents must be explicit. Bug: 65624467 Test: Fixed tests. Change-Id: I8d8a7d7dcc3c85e2b5cd58b0539cdcac062afa7b 
Since O, launching the KeyChainServiceTest in the background does not
work since background execution is limited by default.
Add instructions how to work around this for the test.

Additionally, include the component in the intents to launch the
support & keychain services, as Service Intents must be explicit.

Bug: 65624467
Test: Fixed tests.

Change-Id: I8d8a7d7dcc3c85e2b5cd58b0539cdcac062afa7b
Removing GET_ACCOUNTS permission. 2016-02-16T23:42:34+00:00 Carlos Valdivia carlosvaldivia@google.com 2016-02-12T01:13:32+00:00 4b0333ffbf17356539198a1f84fff38df8684609 It doesn't appear that GET_ACCOUNTS was ever needed in KeyChain and it is going to be non-functional in targetSdkVersion >= 24. Bug: 21901286 Change-Id: Id393d884e1dc5f67863bb0146c589aee3abd9091 
It doesn't appear that GET_ACCOUNTS was ever needed in KeyChain and it is going
to be non-functional in targetSdkVersion >= 24.

Bug: 21901286
Change-Id: Id393d884e1dc5f67863bb0146c589aee3abd9091
Remove obsolete KeyChain references to USE_CREDENTIALS (1 of 2) 2012-03-01T23:14:06+00:00 Brian Carlstrom bdc@google.com 2012-03-01T23:14:06+00:00 db6218b771e86f77740532fc86c6ae4081eacd75 Change-Id: I3838e8cead176043d1066802ff62ba2f4930f579 
Change-Id: I3838e8cead176043d1066802ff62ba2f4930f579
Adding KeyChainService and KeyChainActivity 2011-04-23T00:15:31+00:00 Brian Carlstrom bdc@google.com 2011-04-11T16:05:06+00:00 3e6251dedc92654476c70bdc413f24a4b31ce6a4 Change-Id: I6c862d3e687cf80fb882966adb3245f2244244fe 
Change-Id: I6c862d3e687cf80fb882966adb3245f2244244fe