Securing APIs with Apigee X avis

3204 avis

B Saloni P. · Examiné il y a 12 mois

Arturo Q. · Examiné il y a 12 mois

Paige G. · Examiné il y a 12 mois

Manuel N. · Examiné il y a 12 mois

Humaidi A. · Examiné il y a 12 mois

Damian J. · Examiné il y a 12 mois

眞哉 神. · Examiné il y a environ un an

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. · Examiné il y a environ un an

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. · Examiné il y a environ un an

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. · Examiné il y a environ un an

Getting error on token endpoint

Maurice L. · Examiné il y a environ un an

Getting error on deploy

Maurice L. · Examiné il y a environ un an

didnt got it running in the fault section: Status: instance "eval-instance" reported error beans.MarshalFailure: "java.lang.IllegalArgumentException: argument type mismatch"

Richard K. · Examiné il y a environ un an

Lillian S. · Examiné il y a environ un an

Sangamesh B. · Examiné il y a environ un an

Sangamesh B. · Examiné il y a environ un an

Paweł R. · Examiné il y a environ un an

Arunkumar P. · Examiné il y a environ un an

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. · Examiné il y a environ un an

Aryav V. · Examiné il y a environ un an

Mariana T. · Examiné il y a environ un an

Thomas L. · Examiné il y a environ un an

Andres Felipe P. · Examiné il y a environ un an

Saurabh k. · Examiné il y a environ un an

Masking step did not work, perhaps because I was debugging in the new UI?

Maxwell L. · Examiné il y a environ un an

Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.