I am preparing to initialize Google Cloud Identity Platform in a billing-enabled test project.
The identitytoolkit.googleapis.com API is already enabled, but the authentication configuration returns CONFIGURATION_NOT_FOUND. I have not run initializeAuth yet.
Before calling:
POST /v2/projects/PROJECT_ID/identityPlatform:initializeAuth
I would like to confirm its automatic side effects:
1. Does initialization enable any additional APIs? If so, which ones?
2. Does it automatically create API keys, OAuth clients/client secrets, Firebase resources, or service accounts?
3. Besides the Identity Platform service agent and roles/identitytoolkit.serviceAgent, are any other IAM bindings automatically added?
4. Does the Console's “Enable Identity Platform” action perform additional operations compared with the REST initializeAuth method?
5. Is there a supported dry-run or a way to prevent additional API/IAM changes before they occur?
The intended use is Google sign-in for an existing Cloud Run application. I am not planning to use Firebase Hosting, phone authentication, or reCAPTCHA Enterprise features.
Please point me to official documentation describing these side effects. If this is not the appropriate forum, please suggest the correct place to ask.
Thank you.
