
auth0-java-mvc-common
Use when adding Auth0 login, logout, or callback handling to a Java Servlet web application. Integrates com.auth0:mvc-auth-commons for server-side Java apps — use even if the user says "add login to my Java web app" without naming the library.
- Installs
- 388
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/auth0/agent-skills --skill auth0-java-mvc-common- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads auth0-java-mvc-common automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Auth0 Java MVC Common Integration
Add Auth0 authentication to Java Servlet web applications using com.auth0:mvc-auth-commons. Provides AuthenticationController for building authorize URLs and handling callbacks, with session-based authentication and support for Organizations and Multiple Custom Domains.
Agent instruction: Before providing SDK setup instructions, fetch the latest release version by running:
gh api repos/auth0/auth0-java-mvc-common/releases/latest --jq '.tag_name'Use the returned version in all dependency lines instead of any hardcoded version below. If the API call fails, use
1.12.0.
Prerequisites
- Java 8+ (Java 17+ recommended)
- Servlet container (Tomcat, Jetty, etc.) with javax.servlet 3+
- Maven 3.6+ or Gradle 7+
- Auth0 Regular Web Application configured
- If you don't have Auth0 set up yet, use the
auth0-quickstartskill first
When NOT to Use
| Use Case | Recommended Skill |
|---|---|
| Spring Boot web applications with auto-configuration | Use Spring Boot + Okta starter for auto-configured Spring Boot login |
| Spring Boot REST APIs (stateless JWT) | Use auth0-springboot-api for JWT Bearer token validation |
| Single Page Applications | Use auth0-react, auth0-vue, or auth0-angular for client-side auth |
| Mobile applications | Use auth0-android or auth0-swift for native mobile |
| Machine-to-machine API calls | Use Auth0 Management API SDK for server-to-server |
Quick Start Workflow
Agent instruction: Do not write or echo credential values (domain, client ID, client secret) yourself. If the user's prompt already provides Auth0 credentials, skip the credential questions and instruct the user to populate their
.envfile — provide the variable names and file path but use placeholders (<YOUR_DOMAIN>,<YOUR_CLIENT_ID>,<YOUR_CLIENT_SECRET>), never actual values. Never repeat credentials back in responses.
Secret handling rules:
- Never retrieve or parse
client_secretfrom Auth0 CLI output.- Never write actual credential values into any file using the Write or Edit tool — always use placeholders and instruct the user to substitute their real values.
- Do NOT read
.envfiles (to avoid exposing existing secrets in context).- Always ensure
.envis in.gitignore— add the entry automatically if missing.
1. Install SDK
Gradle (build.gradle):
implementation 'com.auth0:mvc-auth-commons:1.12.0'
Maven (pom.xml):
<dependency>
<groupId>com.auth0</groupId>
<artifactId>mvc-auth-commons</artifactId>
<version>1.12.0</version>
</dependency>
2. Create Auth0 Application
You need a Regular Web Application (not SPA or Native) in Auth0.
STOP — ask the user before proceeding.
Ask exactly this question and wait for their answer before doing anything else:
"How would you like to create the Auth0 application?
- Automated — I'll run Auth0 CLI commands that create the application and write the values to your config automatically.
- Manual — You create the application yourself in the Auth0 Dashboard (or via
auth0 apps create) and provide me the Domain, Client ID, and Client Secret.Which do you prefer? (1 = Automated / 2 = Manual)"
Do NOT proceed to any setup steps until the user has answered. Do NOT default to manual.
If the user chose Automated, follow the Setup Guide for the complete Auth0 CLI steps. The automated path writes configuration for you — skip Step 3 below and proceed directly to Step 4.
If the user chose Manual, follow the Setup Guide (Manual Setup section). Then continue with Step 3.
Quick reference for manual application creation:
# Using Auth0 CLI
auth0 apps create \
--name "My Java Web App" \
--type regular \
--callbacks http://localhost:3000/callback \
--logout-urls http://localhost:3000
Or create manually in Auth0 Dashboard → Applications → Applications → Create Application → Regular Web Applications
3. Configure Credentials
Store credentials as environment variables (never hardcode in source):
export AUTH0_DOMAIN="your-tenant.auth0.com"
export AUTH0_CLIENT_ID="your-client-id"
export AUTH0_CLIENT_SECRET="your-client-secret"
Or use a .env file (add to .gitignore):
AUTH0_DOMAIN=your-tenant.auth0.com
AUTH0_CLIENT_ID=your-client-id
AUTH0_CLIENT_SECRET=your-client-secret
Agent instruction: Never write actual credential values to files. Instead, instruct the user to create or update
.envwith their credentials. Provide the template with placeholders only. Always add.envto.gitignoreif not already present. Warn the user: "Check your.envfor duplicate Auth0 entries if you've configured it previously."Java does not auto-load
.envfiles.System.getenv()only reads OS-level environment variables. If you generate a.envfile, you must also either: (1) add dotenv-java as a dependency and useDotenv.load().get("AUTH0_DOMAIN")instead ofSystem.getenv(), or (2) instruct the user to runsource .envbefore starting the server. Do not generate code that uses both a.envfile andSystem.getenv()without a loading mechanism — the values will benull.
Important: Domain must NOT include https://. The library constructs the issuer URL automatically.
4. Initialize AuthenticationController
Create a singleton AuthenticationController instance:
import com.auth0.AuthenticationController;
import com.auth0.jwk.JwkProviderBuilder;
import com.auth0.jwk.JwkProvider;
public class Auth0Config {
private static final AuthenticationController controller = createController();
private static AuthenticationController createController() {
String domain = System.getenv("AUTH0_DOMAIN");
String clientId = System.getenv("AUTH0_CLIENT_ID");
String clientSecret = System.getenv("AUTH0_CLIENT_SECRET");
JwkProvider jwkProvider = new JwkProviderBuilder(domain).build();
return AuthenticationController.newBuilder(domain, clientId, clientSecret)
.withJwkProvider(jwkProvider)
.build();
}
public static AuthenticationController getAuthController() {
return controller;
}
}
5. Create Login Servlet
import com.auth0.AuthenticationController;
import com.auth0.AuthorizeUrl;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
@WebServlet(urlPatterns = {"/login"})
public class LoginServlet extends HttpServlet {
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
AuthenticationController controller = Auth0Config.getAuthController();
// Build callback URL — omit port for standard ports (80/443) to avoid
// mismatch with the URL registered in Auth0 Dashboard, especially behind proxies.
String scheme = request.getScheme();
int port = request.getServerPort();
String redirectUrl = scheme + "://" + request.getServerName()
+ ((port == 80 || port == 443) ? "" : ":" + port) + "/callback";
AuthorizeUrl authorizeUrl = controller.buildAuthorizeUrl(request, response, redirectUrl)
.withScope("openid profile email");
response.sendRedirect(authorizeUrl.build());
}
}
6. Create Callback Servlet
import com.auth0.AuthenticationController;
import com.auth0.IdentityVerificationException;
import com.auth0.Tokens;
import javax.servlet.ServletException;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.IOException;
@WebServlet(urlPatterns = {"/callback"})
public class CallbackServlet extends HttpServlet {
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
AuthenticationController controller = Auth0Config.getAuthController();
try {
Tokens tokens = controller.handle(request, response);
request.getSession().setAttribute("accessToken", tokens.getAccessToken());
request.getSession().setAttribute("idToken", tokens.getIdToken());
response.sendRedirect("/dashboard");
} catch (IdentityVerificationException e) {
response.sendRedirect("/login?error=" + e.getCode());
}
}
}
7. Protect Routes with Authentication Middleware (Servlet Filter)
import javax.servlet.*;
import javax.servlet.annotation.WebFilter;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import java.io.IOException;
@WebFilter(urlPatterns = {"/dashboard/*", "/api/private/*"})
public class AuthenticationFilter implements Filter {
@Override
public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain)
throws IOException, ServletException {
HttpServletRequest request = (HttpServletRequest) req;
HttpServletResponse response = (HttpServletResponse) res;
HttpSession session = request.getSession(false);
if (session == null || session.getAttribute("idToken") == null) {
response.sendRedirect("/login");
return;
}
chain.doFilter(req, res);
}
@Override
public void init(FilterConfig filterConfig) {}
@Override
public void destroy() {}
}
8. Test Application
Agent instruction: After writing all code, verify the build succeeds:
./gradlew buildor
mvn package. If build fails, diagnose and fix. After 5-6 failed attempts, useAskUserQuestionto get help.
- Start the application and navigate to
http://localhost:3000/login - You should be redirected to the Auth0 Universal Login page
- After login, the callback servlet handles the response and redirects to
/dashboard
Common Mistakes
| Mistake | Fix |
|---|---|
Domain includes https:// | Use your-tenant.auth0.com format only — no scheme prefix |
| Client secret hardcoded in source | Use environment variables or .env file, add to .gitignore |
| Created SPA or Native app instead of Regular Web | Must create Regular Web Application in Auth0 Dashboard |
| Callback URL mismatch | Callback URL in code must exactly match what's registered in Auth0 Dashboard |
Missing openid scope | Always include openid in the scope — required for ID token |
Not handling IdentityVerificationException | Always catch this in the callback handler to show login errors |
Using response_type=token | Regular web apps must use code flow (the default) — never implicit |
| Session not invalidated on logout | Call request.getSession().invalidate() before redirecting to Auth0 logout |
Scope and Audience Configuration
See Integration Guide for requesting custom scopes, audience for API access tokens, and Organizations support.
Multiple Custom Domains (MCD)
Built-in support for routing users to the correct Auth0 domain via DomainResolver. See Integration Guide for configuration.
Related Skills
auth0-quickstart— Basic Auth0 setup and account creationauth0-springboot-api— Spring Boot REST APIs with JWT Bearer token validation
Quick Reference
Core Classes:
AuthenticationController— Main entry point, builds authorize URLs and handles callbacksAuthenticationController.Builder— Configures the controller vianewBuilder(domain, clientId, clientSecret)AuthorizeUrl— Fluent builder for/authorizeURL parametersTokens— Access token, ID token, refresh token from callbackIdentityVerificationException— Authentication error with error codeDomainResolver— Interface for Multiple Custom Domain support
Builder Methods (AuthorizeUrl):
.withScope("openid profile email")— Set requested scopes.withAudience("https://my-api")— Request API access token.withOrganization("org_xxx")— Lock to specific Organization.withInvitation("invite_xxx")— Accept Organization invitation.withConnection("google-oauth2")— Skip to specific connection.withParameter("key", "value")— Add custom authorize parameter
Token Access (Tokens):
tokens.getAccessToken()— Access token stringtokens.getIdToken()— ID token (JWT) stringtokens.getRefreshToken()— Refresh token (ifoffline_accessscope requested)tokens.getExpiresIn()— Token expiration in secondstokens.getType()— Token type (usually "Bearer")tokens.getDomain()— Auth0 domain that issued the tokenstokens.getIssuer()— Token issuer URL
Detailed Documentation
- Setup Guide — Auth0 CLI automation, environment configuration, secret management
- Integration Guide — Organizations, MCD, custom scopes, logout, error handling, advanced patterns
- API Reference — Complete configuration options, builder methods, claims reference, testing checklist
References
FAQ
What does the auth0-java-mvc-common skill do?
Use when adding Auth0 login, logout, or callback handling to a Java Servlet web application. Integrates com.auth0:mvc-auth-commons for server-side Java apps — use even if the user says "add login to my Java web app" without naming the library.
How do I install auth0-java-mvc-common?
Run npx skills add https://github.com/auth0/agent-skills --skill auth0-java-mvc-common in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/auth0-java-mvc-common/ (personal) or .claude/skills/auth0-java-mvc-common/ (project).
Which AI agents can use auth0-java-mvc-common?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is auth0-java-mvc-common safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains auth0-java-mvc-common?
It is published by auth0 in auth0/agent-skills, and it is an official skill from the maker of the technology it covers. It has 388 recorded installs.
More from auth0/agent-skills
auth0
auth0/agent-skills
Use when adding, fixing, or improving how an app authenticates users or protects an API, or when using or configuring any Auth0 feature — signing users in and out, sessions and tokens, guarding routes and endpoints, MFA, passwordless passkey login (WebAuthn), SSO, Organizations, RBAC, custom domains, Universal Portals for hosted account and organization self-service, or Universal Login branding. Also use to audit a tenant's health, security, and plan fit (CheckMate), to debug why an auth flow fails, to migrate from another auth provider, or to set up the Vercel native integration. Covers any web, mobile, or backend framework and every Auth0 SDK, tool, and API. Use even if the user never mentions Auth0.
auth0-quickstart
auth0/agent-skills
Use when adding Auth0 authentication to any app and unsure which SDK or skill to use. Detects the project's framework and routes to the right setup workflow — use this as the entry point even if the user just says "add login to my app" or "set up Auth0" without naming a framework.
auth0-nextjs
auth0/agent-skills
Use when adding Auth0 login, logout, protected pages, or middleware to a Next.js application. Supports App Router and Pages Router with @auth0/nextjs-auth0 — use even if the user says "add login to my Next.js app" or "protect my Next.js routes".
auth0-react
auth0/agent-skills
Use when adding Auth0 login, logout, protected routes, or user sessions to a React SPA. Integrates @auth0/auth0-react — use even if the user says "add login to my React app" or "protect my React routes" without naming the SDK.
auth0-react-native
auth0/agent-skills
Use when adding Auth0 login, logout, or biometric auth to a bare React Native app (not Expo). Integrates react-native-auth0 with native deep linking.
auth0-express
auth0/agent-skills
Use when adding session-based login, logout, or protected routes to an Express.js web application. Integrates express-openid-connect — use even if the user says "add login to my Express app" or "protect my Express routes".
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.