Skip to main content

Authentication & Roles

Security in Nubie is simple but powerful — and built right into your route handlers with these decorators.

🛠 Important Setup: Make sure your Nubie.json file includes a valid jwtSecretKey. Without it, token validation won’t work.

Authentication​

Validates the JWT token present in the request headers. If the token is missing or invalid, it auto-responds with an unauthenticated error — no extra work needed!

@HttpGet("/profile")
@Authentication()
async getProfileAsync(@BearerTokenPayload() user: any) {
  // Runs only if token is valid
}
  • Looks for a standard Authorization: Bearer <token> header.
  • You can get Raw Token using @BearerToken() decorator

Roles​

For endpoints that require specific user roles, use @Roles()!

@HttpPatch("/delete-user")
@Roles("Admin")
async deleteUserAsync() {
  // Token must be valid AND contain role === "Admin"
}
  • Accepts a string or array of strings: 
    @Roles(["Moderator", "Editor"])
  • Auto-validates the token AND checks role field in payload.
  • No need to use @Authentication() separately — role checks already include authentication.

Manual Token Handling with JWTToken Class​

If you need to generate or manually verify tokens (e.g., in CLI tools or non-route logic):

import { JWTToken } from "nubie";

const token = new JWTToken();
token.addClaim("iss", "Nubie");

console.log(await token.generateTokenAsync());

const payload = await JWTToken.verifyTokenAsync(token); // Decodes and validates