https://github.com/clerk/asp-mvc-example
Clerk ASP.net MVC Example
https://github.com/clerk/asp-mvc-example
Last synced: about 2 months ago
JSON representation
Clerk ASP.net MVC Example
- Host: GitHub
- URL: https://github.com/clerk/asp-mvc-example
- Owner: clerk
- Created: 2025-04-15T14:49:00.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-04-15T14:49:45.000Z (over 1 year ago)
- Last Synced: 2025-10-29T06:56:14.839Z (9 months ago)
- Language: HTML
- Size: 3.92 MB
- Stars: 0
- Watchers: 2
- Forks: 3
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Clerk ASP.net MVC Example
A demonstration of using Clerk JWT authentication with ASP.net MVC. This example shows how to integrate Clerk's user authentication with a ASP.net MCV backend API.
## Configuration
```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
```bash
$ dotnet install
```
## Running
Run the server:
```bash
$ dotnet Run
```
The server will be running at `http://localhost:5063`.
## Frontend Integration
From a Clerk React frontend:
```js
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:5063/Home/ClerkJWTS", {
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:5063/Home/GatedData", {
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 /Home/ClerkJWTS - Returns the authenticated user ID
GET /Home/GatedData - 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