Dear @supriyokumar274, we have noted your question and will keep it on our radar to ensure you receive an answer, as we encourage our community members and experts to share their insights.
In the meantime, feel free to explore our community’s past articles on Apigee security features.
here actually we are passing one post request to gcs bucket to upload one file into gcs and we are trying to call the gcs which is in another project and apigee is in another project and the service account we are using to deploy the proxy it is having the permission for token creator
So you need to give an apigee service account the rights to create tokens for your service account, this is the script that I use for that:
# set your project id
GOOGLE_CLOUD_PROJECT=YOUR_PROJECT_ID
# get the project number
PROJECT_NUMBER=$(gcloud projects describe $GOOGLE_CLOUD_PROJECT --format="value(projectNumber)")
# assign token creator role to apigee
gcloud iam service-accounts add-iam-policy-binding \
ai-service@$GOOGLE_CLOUD_PROJECT.iam.gserviceaccount.com \
--member="serviceAccount:service-$PROJECT_NUMBER@gcp-sa-apigee.iam.gserviceaccount.com" \
--role="roles/iam.serviceAccountTokenCreator" --project $GOOGLE_CLOUD_PROJECT
You only have to do this once - I do it when provisioning and setting up all of my service accounts that will be used in Apigee proxies.