1
[Discussion] Which OAuth providers need more configuration?
Source: appwrite/appwrite#12225 · opened by @Meldiron
Background In the past couple of weeks, we have made an effort to improve our Project API (used in the Console and CLI), with the aim of allowing all server SDKs to have capabilities such as managing project platforms, webhooks, auth security settings, and more. Managing connected OAuth applications was one of our focus areas, and we made multiple improvements, including: 1. Separate methods for each provider, so IDE autocomplete is better. For example: project.updateOAuth2GitHub({ enabled: true }) 2. Parameter names terminology accurate with each provider, making it easier to know which value belongs where. For example: project.updateOAuth2Dropbox({ appKey, appSecret }) _(Commonly it's Client ID and Client Secret, but Dropbox chose different terminology)_ 3. Documentation for parameters and response models to include sample values, so it's even easier to recognize where each value belongs. For example: 'Client ID' of Bitly OAuth2 app. For example: d9515…
No pledges yet. Be the first to back this.
Comments
Similar requests
feat: OAuth Provider Group-to-Appwrite Team Mapping
1 vote · 0 comments
Backend: Add TikTok as OAuth provider
0 votes · 0 comments
🚀 Enhancement: Add Webflow OAuth Provider
0 votes · 0 comments
🚀 Enhancement: Account creation on OAuth login should be optional
0 votes · 0 comments
🚀 Enhancement: Vipps MobilePay oauth provider
0 votes · 0 comments
No comments yet.