centersl/dify-docs
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs.git synced 2026-03-27 13:28:32 +07:00
Code Issues Packages Projects Releases Wiki Activity

Documentation edits made through Mintlify web editor

Browse Source
This commit is contained in:
Riskey
2025-09-09 10:10:33 +08:00
committed by GitHub
parent df91b11e94
commit 14a142fa65
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
en/plugins/quick-start/develop-plugins/tool-oauth.mdx
View File

@@ -20,7 +20,7 @@ OAuth in Dify involves **two separate flows** that developers should understand
Admins of Self-Hosted Dify instances must go through this setup flow.
</Note>
Dify instance's admins or developers first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client.
Dify instance's admins or developers first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client.
As an example, here are the steps to setting up an OAuth client for Dify's Gmail tool provider:
@@ -100,7 +100,7 @@ The `oauth_schema` section of the provider manifest definitions tells Dify what
#### client_schema
This defines the input for OAuth client setup:
Defines the input for OAuth client setup:
```yaml gmail.yaml
oauth_schema:
@@ -137,7 +137,7 @@ Specifies what the user authorization flow produces (Dify manages these automati
Include both `oauth_schema` and `credentials_for_provider` to offer OAuth \+ API key auth options.
</Info>
### 2. Complete required OAuth methods in Tool Provider
### 2. Complete Required OAuth Methods in Tool Provider
Add these imports to where your `ToolProvider` is implemented: