jclouds Google Cloud Storage Provider =========================================================== Make sure both Google Cloud Storage and Google Cloud Storage JSON API are enabled for the project (check from Developers Console -> Api&auth -> APIs) * Q. What is the identity for GCE? A. the identity is the developer email which can be obtained from the admin GUI. Its usually something in the form: @developer.gserviceaccount.com * Q. What is the credential for GCE A. the credential is a private key, in pem format. It can be extracted from the p12 keystore that is obtained when creating a "Service Account" (in the GUI: Developers Console(For the project) -> APIs and Auth -> Create New Client ID -> "Service Account" * Q. How to convert a p12 keystore into a pem format jclouds Google Cloud Storage can handle: A. 1. Convert the p12 file into pem format (it will ask for the keystore password, which is usually "notasecret"): openssl pkcs12 -in .p12 -out .pem -nodes 2. Extract only the pk and remove passphrase openssl rsa -in .pem -out .pem The last file (.pem) should contain the pk that needs to be passed to `ContextBuilder.credential()` for the provider `google-cloud-storage`. Running the live tests: --------------------------------------------------------------- 1. Place the following in your ~/.m2/settings.xml in a profile enabled when live: ``` Email address associated with service account -----BEGIN RSA PRIVATE KEY----- MIICXgIBAAKBgQRRbRqVDtJLN1MO/xJoKqZuphDeBh5jIKueW3aNIiWs1XFcct+h ... aH7xmpHSTbbXmQkuuv+z8EKijigprd/FoJpTX1f5/R+4wQ== -----END RSA PRIVATE KEY----- ``` Example identity :- 123451234-abcd01234efgh@developer.gserviceaccount.com (NUMERIC_PREFIX-ALPHANEUMERIC_SUFFIX@developer.gserviceaccount.com) 2. mvn integration-test -pl google-cloud-storage -Plive