[Spike] Simplify OAuth Client Creation Using Adaptor Schemas

Problem

Working with OAuth credentials in Lightning is hard, especially due to the complexity of how OAuth clients are currently created. While OAuth clients are essential to enable OAuth credentials, the process to configure them is too technical and error-prone for regular users.

At the moment, setting up an OAuth client requires:

• An in-depth understanding of how OAuth works.
• Familiarity with the specific OAuth provider.
• Manual input of multiple URLs and scope values.

This complexity makes the experience frustrating even for experienced developers and admins, let alone other users. In most cases, users don’t care about creating OAuth clients. They just want to pick an adaptor and set up a credential that works.

Proposal

Let’s extend our existing adaptor-based schema approach to OAuth clients.

We already define credential types using adaptor schemas (configuration-schema.json), which Lightning uses to render the appropriate forms. We can apply the same idea to OAuth clients.

Plan

• For each adaptor that supports OAuth, define a schema file (oauth-schema.json) that includes:
  • Required URLs (authorization, token, revocation, introspection, userinfo)
  • Required and optional scopes
• When creating an OAuth client in Lightning, users would pick an adaptor.
  • This selection would auto-fill the relevant URLs and scopes.
  • The user would only need to provide the client_id and client_secret.
• If someone still needs to set up a generic OAuth client (not covered by any adaptor), we retain the existing manual form.

Benefits

• Massively improves UX for setting up OAuth clients.
• Reduces risk of user errors.
• Eliminates the need for duplicating detailed OAuth setup docs across adaptors.
• Brings OAuth UX in line with how we already handle other credential types.

Mockup / Reference

Current form (see attached screenshot) is long, intimidating, and hard to fill out without prior knowledge:

Next Steps

• Validate if we can standardize the schema across major OAuth providers.
• Identify which adaptors would benefit first (Google, Microsoft, etc.).
• Define the schema structure for OAuth metadata (URLs + scopes).
• Modify the UI to support schema-based OAuth client creation.