https://github.com/clerk/dropwizard-example
Dropwizard Clerk auth example
https://github.com/clerk/dropwizard-example
Last synced: 3 months ago
JSON representation
Dropwizard Clerk auth example
- Host: GitHub
- URL: https://github.com/clerk/dropwizard-example
- Owner: clerk
- Created: 2025-04-15T15:00:42.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-04-15T15:01:15.000Z (over 1 year ago)
- Last Synced: 2025-04-17T13:09:33.213Z (over 1 year ago)
- Language: Java
- Size: 10.7 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Dropwizard Clerk auth example
A demonstration of using Clerk JWT authentication with Dropwizard. This example shows how to integrate Clerk's user authentication with a Dropwizard backend API.
## Configuration
Set the required environment variables:
```bash
$ export CLERK_API_SECRET_KEY=your_secret_key
# Set authorized parties (comma-separated list of allowed origins)
$ export CLERK_AUTHORIZED_PARTIES=http://localhost:5173
```
## Installation
```commandline
mvn clean install
```
## Running
```commandline
java -jar target/dropwizard-example-1.0-SNAPSHOT.jar server config.yml
```
The server will be running at `http://localhost:8080`.
## Frontend Integration
From a Clerk React frontend:
```javascript
import { useAuth } from '@clerk/clerk-react';
function ApiExample() {
const { getToken } = useAuth();
const fetchData = async () => {
if (getToken) {
// Get the userId or null if the token is invalid
let res = await fetch("http://localhost:8080/clerk_jwt", {
headers: {
"Authorization": `Bearer ${await getToken()}`
}
});
console.log(await res.json()); // {userId: 'the_user_id_or_null'}
// Get gated data or a 401 Unauthorized if the token is not valid
res = await fetch("http://localhost:8080/gated_data", {
headers: {
"Authorization": `Bearer ${await getToken()}`
}
});
if (res.ok) {
console.log(await res.json()); // {foo: "bar"}
} else {
// Token was invalid
}
}
};
return Fetch Data;
}
```
## API Reference
Available endpoints:
- `GET /clerk_jwt` - Returns the authenticated user ID
- `GET /gated_data` - Returns protected data (requires authentication)
## ⚠️ Production Warning
This project is not optimized for production and does not address all best practices that should be configured in a production app. It serves as a design template and should be given appropriate consideration before being used in production.
Issues to address for production use:
- CORS configuration is specific to development environments
- No HTTPS enforcement
- Minimal error handling (especially 401 errors)
- Using development server settings
For production deployment:
1. Configure proper CORS settings for your specific domains
2. Enforce HTTPS for all API communication
3. Implement comprehensive error handling
4. Use a production-grade web server instead of the built-in development server