tree: ade7709c23ac35c86705632fa9ce9a10ef22a623 [path history] [tgz]
  1. aws_credentials_cc.txt
  2. aws_key_arn.txt
  3. bad_access_keys_aws.csv
  4. bad_aws_credentials_cc.txt
  5. bad_aws_key_arn.txt
  6. bad_credentials_aws.csv
  7. bad_gcp_credentials.json
  8. bad_gcp_key_name.txt
  9. BUILD.bazel
  10. credential.json
  11. credentials_aws.cred
  12. credentials_aws.csv
  13. credentials_aws.ini
  14. ecies_private_keyset.bin
  15. ecies_private_keyset2.bin
  16. ecies_public_keyset.bin
  17. ecies_public_keyset2.bin
  18. gcp_key_name.txt
  19. README.md
testdata/README.md

This folder contains AWS and GCP credentials that are used for testing Tink.

AWS

For security reasons, all AWS credentials in this folder are invalid. If you want to run tests that depend on them, please create your own AWS access keys. The credentials are required in several formats expected by different APIs. For example, Java expects the credentials as a properties file. In order to cover all tests across all languages you will have to replace aws_credentials_cc.txt, credentials_aws.cred, credentials_aws.csv and credentials_aws.ini. These can be generated in a similar way to this script.

GCP

For security reasons, all GCP credentials in this folder are invalid. If you want to run tests that depend on them, please create your own Cloud KMS key, and copy the credentials to credential.json and the key URI to gcp_key_name.txt.