You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have developed a web app outside gcp in azure platform that includes a chat application. I want to integrate gemini models in that. I possess an enterprise license for the Gemini subscription and am using service account credentials for authentication. The issue I'm encountering is that the Google OAuth tokens, generated using the service account details, expire after a certain interval.
My goal is for the web app to be continuously running and ready to answer user questions instantly, interfacing with the Gemini model without delay. However, I can't use API Keys or endpoint authentication like the Google AI developers for the enterprise version.
Please help me resolve this issue. How can I ensure my web app remains operational and responsive with continuous authentication?
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
File Name
intro_gemini_python
What happened?
I have developed a web app outside gcp in azure platform that includes a chat application. I want to integrate gemini models in that. I possess an enterprise license for the Gemini subscription and am using service account credentials for authentication. The issue I'm encountering is that the Google OAuth tokens, generated using the service account details, expire after a certain interval.
My goal is for the web app to be continuously running and ready to answer user questions instantly, interfacing with the Gemini model without delay. However, I can't use API Keys or endpoint authentication like the Google AI developers for the enterprise version.
Please help me resolve this issue. How can I ensure my web app remains operational and responsive with continuous authentication?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: