Setup Authentication and Authorization in your React application in seconds without any verification! Suitable for MVP, side projects or hackathon apps.

kunji-node is a Node.js library designed to verify tokens issued by the Kunji authorization server. It comes with an AuthMiddleware that can be easily integrated into your Node.js applications to secure routes and endpoints.

You can use the kunji service to integrate login within minutes.

Also check the frontend react library for client: kunji-react

To install kunji-node, use npm:

npm install kunji-node

or use yarn:

yarn add kunji-node

Checkout Kunji Official Site for more information.

1. Login to Kunji Dashboard.
2. Go to Developer Mode.
3. Register your app by filling only 3 required fields.
4. You will see your App ID and Public Key.

There are two ways to use the authentication middleware in your application:

1. Using the Kunji export to initialize:

import { Kunji } from 'kunji-node';

const { AuthMiddleware } = Kunji(appId, publicKey);

// Your express other routes

app.use(AuthMiddleware); // Use the authentication middleware for all routes

// Rest of the code

2. Directly importing AuthMiddleware with environment variables:

import { AuthMiddleware } from 'kunji-node';

// Your express other routes

app.use(AuthMiddleware); // Use the authentication middleware for all routes

// Rest of the code

Note: The second method requires the environment variables KUNJI_APP_ID and KUNJI_PUBLIC_KEY to be properly configured. If not configured 500 Response will be given whenever the middleware will be used.

Integrate this middleware into Express before routes requiring authentication. Afterward, you can access the user object using req.user in your controller, with the user's unique ID defined as req.user.uid.

Make sure to set the following environment variables for configuration:

• KUNJI_APP_ID: Your Kunji application ID
• KUNJI_PUBLIC_KEY: Your Kunji public key

Example .env (Important: Use double inverted commas for public key when setting in .env):

KUNJI_APP_ID=test
KUNJI_PUBLIC_KEY="-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0QH5YHC2ZmW1w5JYuWeE
YGFU4iXjbDP3HHKO9EiRjWQMiMErHALaHV9WKkgimEMdDmIfPNc6kVgTYTuTTgAa
PL9cdNjJ3qQuPFSR6fx3DL5GUBee99fMQJE0jYhkwO5eyquUMGd1ACss/5bWD1g8
P/saM+Y3BQp2lXse/Z2rsYrgVO1r52iYrqNfkzInj3iS1VrRbIBBnpncSWJPwWap
RdrgZhkitpFOc/jc+wsBZuMKPab7f9o4S8BOJVmO7pG+qY8Bk1kC4OiYyADpErLs
3kOAZZo9IllQJMFZ3C4w7aeTmlZZRchgFhbulHewz7cmN6MtNG6FRE58n9KDFdhY
yQIDAQAB
-----END PUBLIC KEY-----"

After the middleware verifies the request, you can access the token result using req.user. The interface for the access token result is as follows:

When using typescript, use the AuthRequest type from the package to be able to access req.user.

Example:

import { Response, NextFunction, RequestHandler } from 'express';
import { AuthRequest } from "kunji-node"; 
// Important: when importing middleware directly, Kunji env vars should be configured else it will throw error 500 for every authenticated request

const middleware : RequestHandler = (req: AuthRequest, response: Response, nextFunction : NextFunction) => {
    console.log(req.user.uid)
    // your middleware logic
}

1. Pass debug:true in config object while initialization. Example :

const { AuthMiddleware } = Kunji(appId, publicKey, {debug: true});

OR

2. Set KUNJI_ENABLE_DEBUG=true as an environment variable (.env)

kunji-node by default returns error messages in JSON format with an error message and http status code 401. To use a custom error message you can pass a function to set error message and status code in unauthorizedResponse field in config while initialization.

Example :

const { AuthMiddleware } = Kunji(appId, publicKey, {unauthorizedResponse: (type) => {
    if(type === 'NO_TOKEN'){
        return { statusCode : 400, body: { error: "My custom error message and code", xml: false }}; // set xml to true to set Content-Type to application/xml
    }

    if(type === 'INVALID_TOKEN'){
        return { statusCode : 401, body: { error: "You are not allowed here", xml: false}};
    }
}});

You can also set xml as true to set Content-Type: application/xml for the response header.

Contributions are welcome! If you find any issues or have suggestions for improvements, feel free to create an issue or submit a pull request.

This project is licensed under the MIT License.