Skip to main content

​
Feature Guide: GCX Authentication Integration

​
1. Overview

GCX Authentication Integration connects Fiftyknots with the Google Cloud Experience authentication system, giving you secure, streamlined access across the platform. This integration removes authentication friction - you sign in once through Google Cloud credentials and access all your venture building tools without juggling multiple passwords or interruptions. The system supports both standard OAuth flows and server-to-server authentication for API integrations.

​
2. Step-by-Step Guide

​
Signing In with GCX

  1. Navigate to the Login page (/login) and click the “Sign in with Google Cloud” button
  2. Authenticate through Google - you’ll be redirected to Google’s authentication screen where you authorize Fiftyknots to access your account
  3. Return to Fiftyknots - after authorization, you’re redirected to the Auth Callback page (/authcallback) where your session is established
  4. Access your dashboard - once authenticated, you land on your primary dashboard with full access to your projects and tools

​
Generating API Authentication Codes

  1. Access the Developer Dashboard (/developerdashboard) from your account menu
  2. Navigate to API credentials - find the “Generate Auth Code” section
  3. Click “Generate New Code” - the system creates a time-limited authentication code
  4. Copy and exchange the code - use this code in your API integration to exchange it for access tokens via POST /api/v1/auth/exchange-auth-code

​
Managing Active Sessions

  1. Open your Profile settings and select “Security & Sessions”
  2. Review active sessions - see all devices and locations where you’re currently signed in via GET /api/v1/auth/sessions
  3. Revoke suspicious sessions - click “End Session” next to any session you don’t recognize to terminate it immediately using DELETE /api/v1/auth/sessions/:sessionId
  4. Verify your current session - check your session status anytime via GET /api/v1/auth/session

​
3. Common Questions

Q: Do I need a separate Fiftyknots password after enabling GCX authentication?
A: No. Once you authenticate through Google Cloud, you use your Google credentials exclusively. Fiftyknots doesn’t store or require a separate password - your Google account is your identity. Q: What happens if my Google Cloud credentials change?
A: Your existing Fiftyknots sessions remain active until they expire or you sign out. The next time you sign in, you’ll authenticate with your new Google credentials. All your projects and data remain intact - authentication is separate from your venture data. Q: Can I use API access without signing in through the browser?
A: Yes. Generate an auth code from the Developer Dashboard, then exchange it for access tokens using the server-to-server flow via POST /api/v1/auth/exchange-auth-code. This enables headless API access without browser-based OAuth flows. Q: How long do authentication sessions last?
A: Sessions remain active based on your security settings and activity patterns. You can view all active sessions and their creation times through the session management interface. Inactive sessions expire automatically for security. Q: What if I need to sign out from all devices at once?
A: Use the “Sign Out Everywhere” option in your security settings. This invokes POST /api/v1/auth/logout and terminates all active sessions across devices, forcing re-authentication on your next access from any location.

​
4. Troubleshooting

Authentication redirect loop after Google sign-in
Check that third-party cookies are enabled in your browser. GCX authentication requires cookies to establish your session. Clear your browser cache and cookies for both Fiftyknots and Google domains, then try signing in again. “Invalid auth code” error when exchanging for API tokens
Auth codes expire quickly after generation - typically within 5-10 minutes. Generate a fresh code from the Developer Dashboard and exchange it immediately. Store the resulting access tokens securely rather than regenerating codes repeatedly. Session appears active but receives “unauthorized” errors
Your session token may have expired or been revoked. Call GET /api/v1/auth/me to verify your authentication status. If the call fails, sign out completely using POST /api/v1/auth/logout and re-authenticate through the standard flow. Cannot access certain pages despite successful authentication
Authentication confirms your identity but doesn’t grant universal access. Some pages require specific roles or completed onboarding steps. Check your user profile via GET /api/v1/auth/me to see your assigned roles and permissions. Profile Management - After authentication, complete your founder profile to unlock personalized insights and journey recommendations. Your authentication identity links to your profile data, ensuring continuity across all platform features. Developer Onboarding (/developeronboarding) - If you’re building on the Fiftyknots platform, the developer onboarding flow uses GCX authentication to verify your identity and provision API credentials. Your authenticated session carries through to API key generation and testing. Sherpa Dashboard (/sherpadashboard) - Sherpas authenticate through a specialized flow (POST /api/v1/auth/sherpa/verify-otp) that integrates with GCX but includes additional verification steps. Once authenticated, you access client assignments and review workflows under your verified Sherpa identity.