Skip to content
Forums
Forums
How To
Trouble authenticat...
 
Notifications
Clear all

Trouble authenticating to Vertex AI Gemini from callin.io using Service Account (Cloud user)

 
How To
Last Post by system 1 month ago
3 Posts
2 Users
0 Reactions
5 Views
RSS
Creamus_Oy
 Creamus_Oy
(@creamus_oy)
Posts: 2
New Member
Topic starter
 

Hi,

I'm attempting to call the Google Vertex AI Gemini API (e.g., gemini-1.5-pro or gemini-1.0-pro-vision-latest) from callin.io using a Google Service Account credential, but I'm encountering authentication/permission errors.

The Problem:

  1. The callin.io “Google Service Account” credential fails to save when I paste the full JSON key content (error: “Couldn’t connect with these settings” / likely “secretOrPrivateKey must be an asymmetric key…”).
  2. It only saves if I paste just the private key block (-----BEGIN...END-----). The “Upload file” option is not visible in my UI (callin.io Cloud).
  3. However, when using the credential saved this way, API calls via the HTTP Request node fail with either 404 Not Found (even for gemini-1.0-pro-vision-latest in us-central1) or 400/403 Bad Request (e.g., Project 297... is not allowed to use Publisher Model projects/creamusai/...).

Context:

  • callin.io Version: 1.87.1 (latest Beta)
  • callin.io Setup: callin.io Cloud
  • GCP Project checks (APIs enabled: Vertex AI, IAM Credentials; SA roles assigned: Vertex AI User + SA Token Creator; Billing linked & active) all appear correct for the target project (creamusai, number 297...).
  • Multiple new keys have been generated and tested. JSON key syntax has been validated.

It seems there might be an issue with how callin.io Cloud handles the Google Service Account credential in this version, either during the saving process with the full JSON or during the actual authentication request when saved with only the key block. How can I resolve this to successfully call the Vertex AI API?

Thanks!
Marko

 
Posted : 09/04/2025 6:45 am
Creamus_Oy
 Creamus_Oy
(@creamus_oy)
Posts: 2
New Member
Topic starter
 

To isolate the issue, I tested the authentication outside of callin.io using the Google Cloud SDK command line:

  1. I successfully activated the service account using gcloud auth activate-service-account --key-file="<path_to_my_new_key>".json ". It confirmed Activated service account credentials for: [my-service-account-email].
  2. I then successfully generated a Bearer token using gcloud auth print-access-token.
  3. However, when I used this generated Bearer token directly in the callin.io HTTP Request node (using Header Auth: Authorization: Bearer <TOKEN>), the API call still failed with the same 400 Bad Request error: Project 297... is not allowed to use Publisher Model projects/creamusai/....

This seems to confirm the Service Account key and basic GCP permissions are working correctly outside callin.io, but the API call still fails when initiated from the callin.io Cloud environment, even with direct token authentication.

 
Posted : 09/04/2025 7:02 am
system
 system
(@system)
Posts: 332
Reputable Member
 

This thread was automatically closed 90 days following the last response. New replies are no longer permitted.

 
Posted : 08/07/2025 7:02 am
Forum Jump:
  Previous Topic
Next Topic  
Share: