mirror of
https://github.com/encounter/adk-python.git
synced 2026-07-09 18:19:28 -07:00
Josh SorefandCopybara-Service
aa1233608a
Merge https://github.com/google/adk-python/pull/2447 This PR corrects misspellings identified by the [check-spelling action](https://github.com/marketplace/actions/check-spelling) The misspellings have been reported at https://github.com/jsoref/adk-python/actions/runs/16840838898/attempts/1#summary-47711379253 The action reports that the changes in this PR would make it happy: https://github.com/jsoref/adk-python/actions/runs/16840839269/attempts/1#summary-47711380479 Note: while I use tooling to identify errors, the tooling doesn't _actually_ provide the corrections, I'm picking them on my own. I'm a human, and I may make mistakes. I've included a couple of changes to make CI happy. Personally, I object to CI being in a state of "random drive by person who adds a blank line in the middle of a file must fix all the preexisting bugs in the file", but that appears to be the state for this repository. COPYBARA_INTEGRATE_REVIEW=https://github.com/google/adk-python/pull/2447 from jsoref:spelling d85398e7fd154d124d477c6af6181481a01f34e0 PiperOrigin-RevId: 827629615
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
# OAuth Sample
|
|
|
|
## Introduction
|
|
|
|
This sample tests and demos the OAuth support in ADK via two tools:
|
|
|
|
* 1. list_calendar_events
|
|
|
|
This is a customized tool that calls Google Calendar API to list calendar
|
|
events. It pass in the client id and client secrete to ADK and then get back
|
|
the access token from ADK. And then it uses the access token to call
|
|
calendar api.
|
|
|
|
* 2. get_calendar_events
|
|
|
|
This is a google calendar tool that calls Google Calendar API to get the
|
|
details of a specific calendar. This tool is from the ADK built-in Google
|
|
Calendar ToolSet. Everything is wrapped and the tool user just needs to pass
|
|
in the client id and client secret.
|
|
|
|
## How to use
|
|
|
|
* 1. Follow
|
|
https://developers.google.com/identity/protocols/oauth2#1.-obtain-oauth-2.0-credentials-from-the-dynamic_data.setvar.console_name.
|
|
to get your client id and client secret. Be sure to choose "web" as your
|
|
client type.
|
|
|
|
* 2. Configure your `.env` file to add two variables:
|
|
|
|
* OAUTH_CLIENT_ID={your client id}
|
|
* OAUTH_CLIENT_SECRET={your client secret}
|
|
|
|
Note: don't create a separate `.env` file , instead put it to the same
|
|
`.env` file that stores your Vertex AI or Dev ML credentials
|
|
|
|
* 3. Follow
|
|
https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred
|
|
to add http://localhost/dev-ui/ to "Authorized redirect URIs".
|
|
|
|
Note: localhost here is just a hostname that you use to access the dev ui,
|
|
replace it with the actual hostname you use to access the dev ui.
|
|
|
|
* 4. For 1st run, allow popup for localhost in Chrome.
|
|
|
|
## Sample prompt
|
|
|
|
* `List all my today's meeting from 7am to 7pm.`
|
|
* `Get the details of the first event.`
|