The AI trust layer between agents: identity, agreements, safeguards, and outcome intelligence for A2A.

Viewing files at commit 0fc0266ffa14Commit details View latest

docs/SOCIAL_LOGIN_SETUP.md 41 lines · 2.3 KB

Google and GitHub-only login

OpenClasp now renders only Google and GitHub login buttons. The backend does not support an OpenClasp email/password login.

One-time provider setup

In the Descope Console for the OpenClasp project, add https://openclasp.vercel.app under Settings → Project → Approved Domains.
Go to Settings → Authentication Methods → Social Login. Enable Google and GitHub and keep Enable method in API and SDK on; the web application starts the social OAuth flow directly.
For production, choose Use my own account for each provider and paste credentials from the provider applications below. Descope's defaults are suitable only for limited testing.
Do not add email OTP, magic-link, password, passkey, or SSO actions to the project login flow.

Google OAuth application

In Google Cloud Console, create an OAuth client for a web application called OpenClasp.
Add https://openclasp.vercel.app as an authorized JavaScript origin.
In Descope's Google provider configuration, copy the exact OAuth Callback URL into Google as an authorized redirect URI. Without a custom Descope domain this is normally https://api.descope.com/v1/oauth/callback.
Copy the Google client ID and client secret back into Descope, then save.

GitHub OAuth application

In GitHub Settings → Developer settings → OAuth Apps, create an OAuth App named OpenClasp.
Set Homepage URL to https://openclasp.vercel.app.
Set Authorization callback URL to https://api.descope.com/v1/oauth/callback.
Generate a client secret. In Descope's GitHub provider select Use my own account and paste the client ID and secret. Request only user:email if you need an email attribute.

Test

Open https://openclasp.vercel.app/login. Test Google and GitHub in separate private browser windows. Both should return to /dashboard?code=...; the app exchanges the one-time code and removes it from the address bar. A disabled or misconfigured provider shows a clear error.

References: Descope social login settings, Google setup, and GitHub setup.

# Google and GitHub-only login

OpenClasp now renders only Google and GitHub login buttons. The backend does not support an
OpenClasp email/password login.

## One-time provider setup

1. In the Descope Console for the OpenClasp project, add `https://openclasp.vercel.app` under
   **Settings → Project → Approved Domains**.
2. Go to **Settings → Authentication Methods → Social Login**. Enable Google and GitHub and keep
   **Enable method in API and SDK** on; the web application starts the social OAuth flow directly.
3. For production, choose **Use my own account** for each provider and paste credentials from the
   provider applications below. Descope's defaults are suitable only for limited testing.
4. Do not add email OTP, magic-link, password, passkey, or SSO actions to the project login flow.

## Google OAuth application

1. In Google Cloud Console, create an OAuth client for a web application called OpenClasp.
2. Add `https://openclasp.vercel.app` as an authorized JavaScript origin.
3. In Descope's Google provider configuration, copy the exact **OAuth Callback URL** into Google as
   an authorized redirect URI. Without a custom Descope domain this is normally
   `https://api.descope.com/v1/oauth/callback`.
4. Copy the Google client ID and client secret back into Descope, then save.

## GitHub OAuth application

1. In GitHub **Settings → Developer settings → OAuth Apps**, create an OAuth App named OpenClasp.
2. Set Homepage URL to `https://openclasp.vercel.app`.
3. Set Authorization callback URL to `https://api.descope.com/v1/oauth/callback`.
4. Generate a client secret. In Descope's GitHub provider select **Use my own account** and paste
   the client ID and secret. Request only `user:email` if you need an email attribute.

## Test

Open `https://openclasp.vercel.app/login`. Test Google and GitHub in separate private browser
windows. Both should return to `/dashboard?code=...`; the app exchanges the one-time code and
removes it from the address bar. A disabled or misconfigured provider shows a clear error.

References: [Descope social login settings](https://docs.descope.com/auth-methods/oauth/settings),
[Google setup](https://docs.descope.com/auth-methods/oauth/providers/setting-up-your-own-apps/google),
and [GitHub setup](https://docs.descope.com/auth-methods/oauth/providers/setting-up-your-own-apps/github).

1	`# Google and GitHub-only login`
2
3	`OpenClasp now renders only Google and GitHub login buttons. The backend does not support an`
4	`OpenClasp email/password login.`
5
6	`## One-time provider setup`
7
8	1. In the Descope Console for the OpenClasp project, add `https://openclasp.vercel.app` under
9	`Settings → Project → Approved Domains.`
10	`2. Go to Settings → Authentication Methods → Social Login. Enable Google and GitHub and keep`
11	`Enable method in API and SDK on; the web application starts the social OAuth flow directly.`
12	`3. For production, choose Use my own account for each provider and paste credentials from the`
13	`provider applications below. Descope's defaults are suitable only for limited testing.`
14	`4. Do not add email OTP, magic-link, password, passkey, or SSO actions to the project login flow.`
15
16	`## Google OAuth application`
17
18	`1. In Google Cloud Console, create an OAuth client for a web application called OpenClasp.`
19	2. Add `https://openclasp.vercel.app` as an authorized JavaScript origin.
20	`3. In Descope's Google provider configuration, copy the exact OAuth Callback URL into Google as`
21	`an authorized redirect URI. Without a custom Descope domain this is normally`
22	`https://api.descope.com/v1/oauth/callback`.
23	`4. Copy the Google client ID and client secret back into Descope, then save.`
24
25	`## GitHub OAuth application`
26
27	`1. In GitHub Settings → Developer settings → OAuth Apps, create an OAuth App named OpenClasp.`
28	2. Set Homepage URL to `https://openclasp.vercel.app`.
29	3. Set Authorization callback URL to `https://api.descope.com/v1/oauth/callback`.
30	`4. Generate a client secret. In Descope's GitHub provider select Use my own account and paste`
31	the client ID and secret. Request only `user:email` if you need an email attribute.
32
33	`## Test`
34
35	Open `https://openclasp.vercel.app/login`. Test Google and GitHub in separate private browser
36	windows. Both should return to `/dashboard?code=...`; the app exchanges the one-time code and
37	`removes it from the address bar. A disabled or misconfigured provider shows a clear error.`
38
39	`References: [Descope social login settings](https://docs.descope.com/auth-methods/oauth/settings),`
40	`[Google setup](https://docs.descope.com/auth-methods/oauth/providers/setting-up-your-own-apps/google),`
41	`and [GitHub setup](https://docs.descope.com/auth-methods/oauth/providers/setting-up-your-own-apps/github).`