/
Contact usSee pricingStart building

    About B2B SaaS Authentication

    Introduction
    Stytch B2B Basics
    Integration Approaches
      Full-stack overview
      Frontend (pre-built UI)
      Frontend (headless)
      Backend
    Next.js
      Routing
      Authentication
      Sessions
    Migrations
      Overview
      Reconciling data models
      Migrating user data
      Additional migration considerations
      Zero-downtime deployment
      Defining external IDs
      Migrating from Stytch Consumer to B2B
      Exporting from Stytch
    Custom Domains
      Overview

    Authentication

    Single Sign On
    • Resources

      • Overview
        External SSO Connections
        Standalone SSO
    • Integration Guides

      • Start here
        Provider setup
        Backend integration guide
        Headless integration guide
        Pre-built UI integration guide
    OAuth
    • Resources

      • Overview
        Authentication flows
        Identity providers
        Google One Tap
        Provider setup
    • Integration Guides

      • Start here
        Backend integration
        Headless frontend integration
        Pre-built UI frontend integration
    Connected Apps
      Overview
      Getting started with the SDK
      Getting started with the API
      Client types
      OAuth scopes
    • Integration Guides

      • Integrate with an Existing Auth System
        MCP Authorization Overview
        Integrate with a remote MCP server
        Integrate with AI agents
    • Resources

      • Consent Management
    Sessions
    • Resources

      • Overview
        JWTs vs Session Tokens
        How to use Stytch JWTs
        Custom Claims
        Custom Claim Templates
    • Integration Guides

      • Start here
        Backend integration
        Frontend integration
    Email OTP
      Overview
    Magic Links
    • Resources

      • Overview
        Email Security Scanner Protections
    • Integration Guides

      • Start here
        Backend integration
        Headless frontend integration
        Pre-built UI frontend integration
    Multi-Factor Authentication
    • Resources

      • Overview
    • Integration Guides

      • Start here
        Backend integration
        Headless frontend integration
        Pre-built UI frontend integration
    Passwords
    • Resources

      • Overview
        Strength policy
    • Integration Guides

      • Pre-built UI frontend integration
    UI components
      Overview
      Implement the Discovery flow
      Implement the Organization flow
    DFP Protected Auth
      Overview
      Setting up DFP Protected Auth
      Handling challenges
    M2M Authentication
      Authenticate an M2M Client
      Rotate client secrets
      Import M2M Clients from Auth0
    Trusted Auth Tokens
      Overview
      Getting Started with External IDPs
      Getting Started with Custom Auth Factors
    Device History
      New Device Notifications

    Authorization & Provisioning

    RBAC
    • Resources

      • Overview
        Stytch Resources & Roles
        Role assignment
    • Integration Guides

      • Start here
        Backend integration
        Headless frontend integration
    SCIM
    • Resources

      • Overview
        Supported actions
    • Integration Guides

      • Using Okta
        Using Microsoft Entra
    Organizations
      Managing org settings
      JIT Provisioning

    Testing

    E2E testing
    Sandbox values
Get support on SlackVisit our developer forum

Contact us

B2B SaaS Authentication

/

Guides

/

Authentication

/

Connected Apps

/

Integration Guides

/

Integrate with an Existing Auth System

Add Stytch Connected Apps to an Existing Authentication System

You can use Connected Apps to make your application an OIDC/OAuth2.1 provider without migrating your entire authentication system to the Stytch platform. Any authentication system that issues a JWT access_token or id_token with an email claim can be used here with the help of Trusted Auth Tokens.

When used in this manner, Stytch will be responsible for all OAuth client management, user consent, and token issuance. Your existing authentication system will remain in control of the user's login experience and account information.

Create a Trusted Auth Token Profile

Create a Trusted Auth Token Profile to configure Stytch to accept JWTs issued by your existing Identity Provider. The Trusted Auth Token Profile tells Stytch how to validate these JWTs, and how to map claims like the user's role information to constructs in the Stytch platform.

Keep track of the profile_id created from this step.

2
Add the Stytch Javascript SDK

Install the Javascript SDK to access the Stytch UI component used to handle the OAuth consent flow. The OAuthAuthorize component shown below wraps the B2BIdentityProvider React component. This component will take in a JWT issued by your existing authentication system matching the profile you created above.

The styling and copy of the IdentityProvider UI component can be customized to match your existing application. See available options in the B2BIdentityProvider API reference.

import { useMemo } from 'react';
import { StytchB2BUIClient } from '@stytch/vanilla-js/b2b';
import { StytchB2BProvider, B2BIdentityProvider } from '@stytch/react/b2b';

const stytch = new StytchUIClient('PUBLIC_TOKEN');

// The Trusted Auth Token Profile ID created in Step 1
const tokenProfileID = "trusted-token-profile-...";

export const OAuthAuthorizeComponent = ({ trustedAuthToken }) => {
  const tokenParams = useMemo(() => ({ trustedAuthToken, tokenProfileID }), 
    [trustedAuthToken]);
  
  return (
    <StytchB2BProvider stytch={stytch}>
      <B2BIdentityProvider trustedAuthTokenParams={tokenParams} />
    </StytchB2BProvider>
  )
}

3
Handle Unauthenticated Users

The OAuth Authorization page takes in numerous arguments from OAuth clients in the form of query parameters. If the user is not logged in, your application should redirect them to your existing login implementation. After login, your application should redirect the user back to the exact same URL - preserving the OAuth query parameters for Stytch to handle.

Your existing auth and routing libraries likely have first-class functionality to do this already - consult their documentation for details.

// If the user is unauthenticated, store the full location to return to
// query parameters and all
export const redirectToLogin = (returnState) => {
  localStorage.setItem('returnTo', returnState);
  window.location.href = '/login'
}

// After the user has authenticated, redirect them back
// into the previous OAuth flow
const onLoginComplete = () => {
  const returnTo = localStorage.getItem('returnTo')
  if (returnTo) {
    localStorage.deleteItem('returnTo');
    window.location.href = returnTo;
  } else {
    window.location.href = '/home';
  }
}

4
Implement the OAuth Authorization Page

Define a new page in your application for handling OAuth Authorization. Most commonly, this page lives at ${yourDomain}/oauth/authorize. OAuth clients will redirect the user to this page to kick off an OAuth login flow.

This page should retrieve the JWT from your existing authentication system and pass it in to the OAuthAuthorizeComponent we defined earlier.

import { useState, useEffect } from 'react';
import { createClient } from '@supabase/supabase-js';
import { OAuthAuthorizeComponent } from './components';

const supabase = createClient(
  'https://<project>.supabase.co', 
  '<sb_publishable_... or anon key>',
);

export default function OAuthAuthorizePage() {
  const [session, setSession] = useState(null)
  useEffect(() => {
    supabase.auth.getSession().
      then(({ data: { session } }) => {
        if(!session) {
          // Redirect to login page
          return redirectToLogin(window.location.href)
        }
        setSession(session);
      })
  }, []);
  
  return session ? 
    <OAuthAuthorizeComponent trustedAuthToken={session.access_token} /> :
    null;
}
import { useState, useEffect } from 'react';
import { getAuth } from "firebase/auth";
import { OAuthAuthorizeComponent } from './components';

const auth = getAuth();

export default function OAuthAuthorizePage() {
  const [token, setToken] = useState(null)
  useEffect(() => {
    if (!auth.currentUser) {
      // Redirect to login page
      return redirectToLogin(window.location.href)
    }
    auth.currentUser.getIdToken().
      then((token) => setToken(session))
  }, []);
  
  return session ? 
    <OAuthAuthorizeComponent trustedAuthToken={token} /> :
    null;
}
import { useState, useEffect } from 'react';
import { fetchAuthSession } from 'aws-amplify/auth';
import { OAuthAuthorizeComponent } from './components';

export default function OAuthAuthorizePage() {
  const [token, setToken] = useState(null)
  useEffect(() => {
    fetchAuthSession()
      .then((session) => setToken(session.tokens.idToken))
      // Redirect to your login page if the user is not logged in
      .catch(err => redirectToLogin(window.location.href))
    
  }, []);
  
  return session ? 
    <OAuthAuthorizeComponent trustedAuthToken={token} /> :
    null;
}
import { useState, useEffect } from 'react';
import { Auth0Client } from '@auth0/auth0-spa-js';
import { OAuthAuthorizeComponent } from './components';

const auth0 = new Auth0Client({
  domain: '{yourDomain}',
  clientId: '{yourClientId}'
});

export default function OAuthAuthorizePage() {
  const [token, setToken] = useState(null)
  useEffect(() => {
    auth0.getIdTokenClaims()
      then((claims) => setToken(claims.__raw))
    // Redirect to your login page if the user is not logged in
    .catch(err => redirectToLogin(window.location.href))
  }, []);
  
  return session ? 
    <OAuthAuthorizeComponent trustedAuthToken={token} /> :
    null;
}

5
Configure the Authorization URL in Stytch

In the Connected Apps section of the Stytch Dashboard, set the Authorization URL to the URL of the page where OAuthAuthorizeComponent is mounted. This will allow Stytch to broadcast the URL to clients using your project's OpenID Connect Endpoint.

Entering the Authorization URL

6
Validate Stytch-issued OAuth Access Tokens

After completion of an OAuth flow, the OAuth client will be granted a Stytch-issued Access Token, and optionally an ID Token. The OAuth client can now use this access token to invoke API endpoints hosted by your application. Use the Stytch Backend SDKs - or any JWT-compatible library - to validate the access token within your existing codebase. Refer to the Authenticate Access Token API docs for a complete reference.

from stytch import B2BClient

client = B2BClient(
    project_id="PROJECT_ID",
    secret="SECRET",
    custom_base_url="${projectDomain}",
)

resp = client.idp.introspect_access_token_local(
    access_token="eyJ...",
)
import * as stytch from 'stytch';

const client = new stytch.B2BClient({
  project_id: 'PROJECT_ID',
  secret: 'SECRET',
  custom_base_url: '${projectDomain}',
});

client.idp.introspectTokenLocal({ token: 'eyJ...' })
  .then((resp) => {
    console.log(resp);
  })
  .catch((err) => {
    console.log(err);
  });
require 'stytch'

client = StytchB2B::Client.new(
  project_id: 'PROJECT_ID',
  secret: 'SECRET'
  custom_base_url: '${projectDomain}',
)

resp = client.idp.introspect_token_local(
    token="eyJ...",
)

print(resp)
package main

import (
	"context"
	"log"

	"github.com/stytchauth/stytch-go/v16/stytch/b2b/b2bstytchapi"
	"github.com/stytchauth/stytch-go/v16/stytch/b2b/idp"
)

func main() {
	client, err := b2bstytchapi.NewClient(
		"PROJECT_ID",
		"SECRET",
		b2bstytchapi.WithBaseURI("${projectDomain}"),
	)
	if err != nil {
		log.Fatalf("error instantiating client: %v", err)
	}

	resp, err := client.IDP.IntrospectTokenLocal(
	  context.Background(), 
	  &idp.IntrospectTokenLocalParams{
		  Token: token,
	  })
	if err != nil {
		log.Fatalf("error in method call: %v", err)
	}

	log.Println(resp)
}

What's Next

Your application is now an OAuth 2.1 / OIDC Compliant identity provider!

  • Read about OAuth for MCP
  • Learn more about OAuth Scopes in the Stytch platform

Create a Trusted Auth Token Profile

2.

Add the Stytch Javascript SDK

3.

Handle Unauthenticated Users

4.

Implement the OAuth Authorization Page

5.

Configure the Authorization URL in Stytch

6.

Validate Stytch-issued OAuth Access Tokens

What's Next