Como proteger APIs com a Apigee X avaliações
3254 avaliações
B Saloni P. · Revisado há about 1 year
Arturo Q. · Revisado há about 1 year
Paige G. · Revisado há about 1 year
Manuel N. · Revisado há about 1 year
Humaidi A. · Revisado há about 1 year
Damian J. · Revisado há about 1 year
眞哉 神. · Revisado há about 1 year
3rd try again went wrong like the first try. I had to manually configure the iam: gcloud iam service-accounts create apigee-internal-access --display-name="apigee-proxy" Created service account [apigee-internal-access]. student_00_9ce03718e49e@cloudshell:~ (qwiklabs-gcp-02-6fcfce5783f2)$ gcloud projects add-iam-policy-binding ${GOOGLE_CLOUD_PROJECT} --member="serviceAccount:apigee-internal-access@${GOOGLE_CLOUD_PROJECT}.iam.gserviceaccount.com" --role="roles/iam.serviceAccountUser" 2nd try again went from the beginning wrong: gcloud run services describe simplebank-rest --platform managed --region us-central1 --format 'value(status.url)' ERROR: (gcloud.run.services.describe) Cannot find service [simplebank-rest] How can you provide such rubbish education? I followed everything but I got Error Deploying Revision to eval permission 'iam.serviceAccounts.actAs' denied on resource 'projects/-/serviceAccounts/apigee-internal-access@qwiklabs-gcp-03-60ade244b8e0.iam.gserviceaccount.com' (or it may not exist in the project for Apigee org "qwiklabs-gcp-03-60ade244b8e0"). Really rubbish!
Vladimir H. · Revisado há about 1 year
2nd try again went from the beginning wrong: gcloud run services describe simplebank-rest --platform managed --region us-central1 --format 'value(status.url)' ERROR: (gcloud.run.services.describe) Cannot find service [simplebank-rest] How can you provide such rubbish education? I followed everything but I got Error Deploying Revision to eval permission 'iam.serviceAccounts.actAs' denied on resource 'projects/-/serviceAccounts/apigee-internal-access@qwiklabs-gcp-03-60ade244b8e0.iam.gserviceaccount.com' (or it may not exist in the project for Apigee org "qwiklabs-gcp-03-60ade244b8e0"). Really rubbish!
Vladimir H. · Revisado há about 1 year
I followed everything but I got Error Deploying Revision to eval permission 'iam.serviceAccounts.actAs' denied on resource 'projects/-/serviceAccounts/apigee-internal-access@qwiklabs-gcp-03-60ade244b8e0.iam.gserviceaccount.com' (or it may not exist in the project for Apigee org "qwiklabs-gcp-03-60ade244b8e0"). Really rubbish!
Vladimir H. · Revisado há about 1 year
Getting error on token endpoint
Maurice L. · Revisado há about 1 year
Getting error on deploy
Maurice L. · Revisado há about 1 year
didnt got it running in the fault section: Status: instance "eval-instance" reported error beans.MarshalFailure: "java.lang.IllegalArgumentException: argument type mismatch"
Richard K. · Revisado há about 1 year
Lillian S. · Revisado há about 1 year
Sangamesh B. · Revisado há about 1 year
Sangamesh B. · Revisado há about 1 year
Paweł R. · Revisado há about 1 year
Arunkumar P. · Revisado há about 1 year
First attempt eval wasn't ready after waiting 30 minutes. Second attempt cloud run instance wasn't created. Third attempt worked. In first attempt, it took me forever to realize that oauth.properties had a space at the beginning of the name; maybe add a copy option. Please add the service account to publish to eval to the left menu (with the username and password); I tested this through the non-classic console and scrolling to the top to copy the service account was annoying. Debug did not mask balance on the first call, it did mask the secret, and both were masked on second call.
Lucas S. · Revisado há about 1 year
Aryav V. · Revisado há about 1 year
Mariana T. · Revisado há about 1 year
Thomas L. · Revisado há about 1 year
Andres Felipe P. · Revisado há about 1 year
Saurabh k. · Revisado há about 1 year
Masking step did not work, perhaps because I was debugging in the new UI?
Maxwell L. · Revisado há about 1 year
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.