Add OAuth 2.0 as recommended authentication method#351
Merged
Conversation
Updated getting-started documentation for both zh-CN and en: **Changes:** - Added OAuth 2.0 as the recommended authentication method (marked with ⭐) - Moved traditional API Key method to secondary position for compatibility - Added OAuth registration and authorization flow examples for all SDKs - Included OAuth benefits and security best practices - Provided code examples for Python, JavaScript, Rust, and Java **OAuth 2.0 Benefits:** ✅ More secure (no shared secret) ✅ Simpler integration (no signature calculation) ✅ Token-based modern authentication ✅ Better suited for modern applications Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Added OAuth 2.0 documentation for Traditional Chinese (zh-HK): **Changes:** - Added OAuth 2.0 as the recommended authentication method (marked with ⭐) - Moved traditional API Key method to secondary position for compatibility - Added OAuth registration and authorization flow examples for all SDKs - Included OAuth benefits and security best practices - Provided code examples for Python, JavaScript, Rust, and Java **OAuth 2.0 優勢：** ✅ 更安全（無需共享金鑰） ✅ 更簡單（無需計算簽名） ✅ 基於 Token 的現代認證方式 ✅ 更適合現代應用程式 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Changed OAuth 2.0 authentication documentation to recommend using each language's standard OAuth libraries instead of SDK-provided OAuth classes. **Changes:** - Python: Use requests-oauthlib for OAuth flow - Node.js: Use simple-oauth2 for OAuth flow - Java: Use Spring Security OAuth2 or similar - Rust: Keep using SDK's built-in OAuth implementation This approach: - Reduces SDK maintenance burden - Gives users more flexibility and control - Leverages well-tested standard libraries - SDK only provides Config.from_oauth() method All language versions updated (zh-CN, en, zh-HK). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated getting-started documentation for both zh-CN and en:
Changes:
OAuth 2.0 Benefits:
✅ More secure (no shared secret)
✅ Simpler integration (no signature calculation)
✅ Token-based modern authentication
✅ Better suited for modern applications