Google Application Integration · Authentication profiles
PRINCIPAL needs roles/iam.serviceAccountUser to save this auth config
Short answer
This Application Integration error means someone creates or edits a Service account or OIDC token authentication profile without permission to act as its service account. Grant the Service Account User role on the service account named in the profile to whoever manages the profile.
VerifiedLast verified
01Error text
PRINCIPAL needs roles/iam.serviceAccountUser on SERVICE_ACCOUNT (or its project) to save this auth config.02Likely causes
- Someone creates or edits a Service account or OIDC token authentication profile without permission to act as its service account.
03How to fix it
- Grant the Service Account User role on the service account named in the profile to whoever manages the profile.
04Official documentation
→Related errors
- PRINCIPAL needs roles/iam.serviceAccountUser to run this integrationThis Application Integration error means the person, automation or trigger that starts an integration cannot act as its run-as service account. Grant the Service Account User role to whoever starts the integration. For a trigger, that is the trigger's service account.
- Set a run-as service account. These triggers run with no callerThis Application Integration error means an integration created on or after October 15, 2026, with a trigger other than API or Private, has no run-as service account. Set a run-as service account on the integration.
- Your project requires a run-as service accountThis Application Integration error means a run without user credentials has no run-as service account, in a region where integration governance is enabled. Set a run-as service account on the integration before you publish or test.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.