https://github.com/googleworkspace/drive-cse-upload
https://github.com/googleworkspace/drive-cse-upload
Last synced: 11 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/googleworkspace/drive-cse-upload
- Owner: googleworkspace
- License: apache-2.0
- Created: 2024-07-08T21:14:35.000Z (almost 2 years ago)
- Default Branch: master
- Last Pushed: 2025-04-09T19:14:43.000Z (about 1 year ago)
- Last Synced: 2025-05-29T18:57:39.110Z (12 months ago)
- Language: Python
- Size: 25.4 KB
- Stars: 4
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Drive CSE Upload
With
[Google Workspace Client-side encryption](https://support.google.com/a/answer/10741897)
(CSE), you can add another layer of encryption to your organization's data —
like files and emails — in addition to the default encryption that Google
Workspace provides.
For select Google Workspace editions, admins can import sensitive files from
third-party storage using Client-side encryption and the
[Google Drive API](https://developers.google.com/drive/api/guides/about-sdk),
preserving the confidentiality of your data. Eligible admins can apply for beta
access using
[this form](http://docs/forms/d/e/1FAIpQLSfCROxYOykvmIiEx0X7rdsGqQwb4iXjc_PJVw83QGNHisgh0A/viewform).
In this package we are providing a code sample (in the form of a Python library)
to upload files hosted locally to Google Drive as Client-side encrypted (CSE)
files.
## Project Prerequisites
### Google Cloud
- Have a [Cloud](https://console.cloud.google.com/) project
- Have Google Drive API
[enabled](https://developers.google.com/workspace/guides/view-turn-off-apis)
for the project
- Have a user with an admin rights in that project
- Have a
[service-account](https://developers.google.com/identity/protocols/oauth2#serviceaccount)
configured for the project
- Have the service-account provisioned for
[Domain Wide Delegation](https://support.google.com/a/answer/162106)
- Store the Service Account Private Key File downloaded during the account
creation
Note: The file is only downloaded during creation; you cannot re-download it
### Identity Provider (IDP)
- Have an OAuth Client ID for Desktop
- Download and store the Client Secret File for the configured OAuth Client Id
### Google Admin Console
- Have [CSE](https://support.google.com/a/answer/14309952) configured for the
domain
- Have an IDP [configured](https://support.google.com/a/answer/10743588) for
the domain
- Have a
[KACLS](https://developers.google.com/workspace/cse/guides/configure-service)
configured for the domain
### Key ACL Service (KACLS)
- The KACLS must support the `/privilegedwrap`, `/privilegedunwrap`, and
`/digest` endpoints
- Have the KACLS configured for the domain allow `/privilegedwrap` and
`/privilegedunwrap` by the admin user
- Have the KACLS configured for the domain allow `/digest` by Google
- See https://developers.google.com/workspace/cse/reference
## Installing this Package
The easiest way to install this package is to get it from [PyPi](https://pypi.org/project/drive-cse-upload/):
```shell
pip install drive-cse-upload
```
This will get this package and all of its dependencies.
Details
If you get this package from GitHub, you'll need to install its dependencies separately.
##### Python
- Python 3.10.7 or greater
##### Tink Cryptographic Library
- https://developers.google.com/tink
```shell
pip3 install tink>=1.10.0
```
##### Google Client Library
- https://developers.google.com/drive/api/quickstart/python
```shell
pip install --upgrade google-api-python-client google-auth-httplib2 google-auth-oauthlib
```
## Running the Example
- Set these parameters to match your setup
- `SA_KEY_FILE`: The Service Account Private Key File
- `CLIENT_SECRET_FILE`: The OAuth Client Secret File
- `SAVED_CREDS_FILE`: Where to store the IDP Oauth credentials
- `AS_USER`: Upload the file as this user (an email-address)
- `INPUT_FILE` The file to upload
- `PARENT_ID` The parent folder/shared-drive for the uploaded file
(optional)
Note: The first three files listed above contain sensitive information that
should be protected. Users must ensure that the files passed-in / created
are not readable by anyone but their owner.
```shell
$ python example.py \
--sa-key-file "${SA_KEY_FILE}" \
--client-secret-file "${CLIENT_SECRET_FILE}" \
--saved-creds-file "${SAVED_CREDS_FILE}" \
--as-user "${AS_USER}" \
"${INPUT_FILE}"
```
This will upload and validate the file `${INPUT_FILE}` to `${AS_USER}`'s root
MyDrive.
```shell
$ python example.py \
--sa-key-file "${SA_KEY_FILE}" \
--client-secret-file "${CLIENT_SECRET_FILE}" \
--saved-creds-file "${SAVED_CREDS_FILE}" \
--as-user "${AS_USER}" \
--parent-id "${PARENT_ID}" \
"${INPUT_FILE}"
```
This will upload and validate the file `${INPUT_FILE}` as a child of the folder
or shared-drive designated by `${PARENT_ID}`.
As part of the upload process, you'll be prompted to open a browser window with
a URL for authenticating with the IDP. Enter the admin user credentials there to
continue.
When done, the code will print the name and the id of the newly uploaded file.
You can see the file in the Drive web client. To ensure that the file is
uploaded correctly, now try the "Download and decrypt" action. This should
download the decrypted file to your local host.