crypto-project | Project for the Crypto subject at Uni | Cryptography library
kandi X-RAY | crypto-project Summary
kandi X-RAY | crypto-project Summary
Project for the Crypto subject at Uni
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of crypto-project
crypto-project Key Features
crypto-project Examples and Code Snippets
Community Discussions
Trending Discussions on crypto-project
QUESTION
It's not clear from the documentation how one might wield Google Key Management System (KMS) on Google App Engine Standard, particularly when developing locally using the development server.
It would appear as reasonably straightforward as:
- Installing
google-api-python-client
in a Python virtual env (and adding the virtualenv path withgoogle.appengine.ext.vendor
inappengine_config.py
) - importing
googleapiclient.discovery
- getting the application identity with
google.appengine.api.app_identity
- Using the
kms
client in the anticipated / documented way
... then following the tutorial linked in the Documentation. However my attempts so far have not resulted in success, and it appears the documentation is wanting for a few steps.
It feels like I'm breaking new ground that I'm sure others must have already.
Has anyone documented using Google KMS on App Engine Standard & its local development server?
EDIT - Update with Code ExampleHere's some code that illuminates -- the problem would appear to be with my setup of default credentials.
mykms.py
...ANSWER
Answered 2017-Jun-30 at 15:33If you're developing using Cloud KMS in GAE, there isn't a local dev service, you can only talk to the main production service as you've gathered. You could use the libraries as you've detailed to develop locally, but would still be hitting production.
Note that you'll have to give GAE application default credentials with a scope for use, see https://cloud.google.com/kms/docs/accessing-the-api#google_app_engine
You can also make requests as the GAE service account if you use
gcloud iam service-accounts keys
and gcloud auth activate-service-account
.
In general, for a dev environment, you might want to segment this as a separate KeyRing (or even a separate project) from your production resources.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install crypto-project
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page