insforge--insforge/.archive/docs/deprecated/insforge-auth-sdk.md

InsForge Auth SDK

Setup

import { createClient } from '@insforge/sdk';
const client = createClient({ baseUrl: 'http://localhost:7130' });

Methods

signUp

await client.auth.signUp({ email, password, name? })
// Returns: { data: { accessToken, user }, error }
// user: { id, email, name, emailVerified, createdAt, updatedAt }
// Token auto-stored

signInWithPassword

await client.auth.signInWithPassword({ email, password })
// Returns: { data: { accessToken, user }, error }
// Token auto-stored

signInWithOAuth

const { data, error } = await client.auth.signInWithOAuth({ 
  provider: 'google'|'github', 
  redirectTo: window.location.origin,
  skipBrowserRedirect: true
})
// Returns: { data: { url, provider }, error }

// Manual redirect required
if (data?.url) {
  window.location.href = data.url
}

// ⚠️ IMPORTANT: No callback handling needed!
// After OAuth, user returns to redirectTo URL already authenticated
// The SDK automatically:
// - Handles the OAuth callback
// - Stores the JWT token
// - Makes user available via getCurrentUser()

// ❌ DON'T DO THIS (not needed):
// const accessToken = urlParams.get('access_token')
// const userId = urlParams.get('user_id')

// ✅ DO THIS INSTEAD (after redirect back):
const { data: userData } = await client.auth.getCurrentUser()

getCurrentUser

await client.auth.getCurrentUser()
// Returns: { data: { user: { id, email, role }, profile: {...} }, error }
// Makes API call to validate token and fetch profile

getCurrentSession

await client.auth.getCurrentSession()
// Returns: { data: { session: { accessToken, user } }, error }
// From localStorage, no API call

getProfile

await client.auth.getProfile(userId)
// Returns: { data: { id, nickname, bio, ... }, error }
// Returns single object, not array!

setProfile

await client.auth.setProfile({ nickname, bio, avatar_url })
// Returns: { data: { id, nickname, bio, ... }, error }
// Returns single object, not array!

signOut

await client.auth.signOut()
// Returns: { error }
// Clears token from storage

Error Codes

• INVALID_EMAIL
• WEAK_PASSWORD
• USER_ALREADY_EXISTS
• INVALID_CREDENTIALS
• INVALID_TOKEN

Notes

• Tokens stored in localStorage (browser) or memory (Node.js)
• All requests after login automatically include token
• User profile data in users table, not auth