Skip to main content
You’ve got your own authentication system. We get it. Rather than making users log in twice, you can seamlessly pass them from your platform into Nudj. We support two approaches depending on your setup.
Settings Location: Navigate to Control Room > Settings > User Authentication to configure custom login methods.

Choose Your Path

The method you choose depends on where your users are in their journey.

Decision Matrix

Not sure which one fits your use case? This should help:
ScenarioUse This
Users are in your app → you want to show Nudj inlineAPI Link
Users are in your app → you want to open Nudj in a new tabAPI Link
Users navigate directly to Nudj’s URLOAuth
You want the fewest steps for your usersAPI Link
You’re following industry-standard auth patternsOAuth
Your users need to authenticate to multiple servicesOAuth

Implementation Details

Both methods are secure and production-ready. The main difference is orchestration: who’s coordinating the login flow? API Link: Your system is the coordinator. You hold the credentials and decide when/how to send users to Nudj. OAuth: Both systems coordinate together through standardized protocols.

API Link User Token Authentication

Step-by-step guide for generating secure JWT tokens and auto-signing users into Nudj.View API Link Guide →

OAuth Integration Setup

Configure your OAuth provider to work with Nudj’s OpenID Connect flow.View OAuth Guide →

Quick Setup Comparison

  1. Set up OIDC configuration in Nudj (provide issuer, clientId, clientSecret)
  2. Nudj generates a callback URL
  3. Add that callback URL to your OAuth provider’s whitelist
  4. User clicks “Log in” at Nudj
  5. User authenticates with your provider
  6. User is redirected back to Nudj, fully authenticated
Full details →
Not sure which to pick? If you’re embedding Nudj inside your app or redirecting from one of your pages, go API Link. If Nudj is accessed directly and you want a standard auth flow, go OAuth.
Both methods are secure: API Link uses signed JWT tokens. OAuth uses industry-standard token exchange. Neither exposes user credentials unnecessarily.