Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
jwt-mongo-sms
Advanced tools
If you're wondering how to implement authentication with JSON web tokens, Mongo DB, Twilio SMS, and (optionally) GraphQL, you're in the right place!
npm install jwt-mongo-sms
or
yarn add jwt-mongo-sms
(Before doing anything with this package, you'll need a Mongo database and a Twilio account with a phone number to use for SMS.)
Create an instance of JwtMongoSms
:
import JwtMongoSms from 'jwt-mongo-sms';
const {
JWT_SECRET,
MONGODB_URI,
TWILIO_ACCOUNT_SID,
TWILIO_AUTH_TOKEN,
TWILIO_SMS_PHONE_NUMBER,
} = process.env;
const jwtMongoSms = new JwtMongoSms({
jwtSecret: JWT_SECRET,
mongoUri: MONGODB_URI,
twilio: {
accountSid: TWILIO_ACCOUNT_SID,
authToken: TWILIO_AUTH_TOKEN,
phoneNumber: TWILIO_SMS_PHONE_NUMBER,
},
});
export default jwtMongoSms;
Add the middleware to your server:
import express from 'express';
import jwtMongoSms from './jwtMongoSms'; // from wherever you instantiated JwtMongoSms
const server = express();
server.use(jwtMongoSms.getAuthMiddleware());
Using this middleware and the sendAuthCode
and verifyAuthCode
methods (see API and Examples below), you can check request.user
in each server request to determine which user (if any) has been authenticated!
NOTE: You will need to store the JSON web token on the client using localStorage
, cookies, or another method, and send it via the request Authorization
header. (See the GraphQL example below.)
There are three required fields when instantiating a JwtMongoSms
object: jwtSecret
, mongoUri
, and twilio
. Configuring the rest is optional.
Field | Default Value | Description |
---|---|---|
jwtSecret | JSON web token secret | |
mongoUri | Mongo URI (e.g., mongodb://localhost/my-db ) | |
twilio | {} | Twilio credentials (accountSid , authToken ) and phoneNumber used to send SMS text |
setSmsMessage | (authCode => `Your authentication code is ${authCode}`) | Used to set the message for SMS authentication |
usersCollectionName | users | Name of the Mongo collection used to store user data |
authCollectionName | users | Name of the Mongo collection used to store auth data |
requestKey | user | Key your authenticated user will be assigned to on each server request |
authCodeLength | 4 | Length of authentication code |
authCodeTimeoutSeconds | 600 | Number of seconds it takes for a authentication code to expire |
decodeUserId | (userId => ObjectId.createFromHexString(userId)) | Determines the format of _id for the auth middleware user query. If your user ids are stored as strings instead of ObjectIds (e.g., Meteor), you should replace this with (userId) => userId) |
The following are methods from the JwtMongoSms
class you can use (from an instantiated object):
getAuthMiddleware() : express.Handler[]
sendAuthCode(phoneNumber: string) : Promise<boolean>
phoneNumber
with new authCode
and authCodeCreatedAt
. NOTE: By default userCollectionName
and authCollectionName
are both set to users
. That means if you don't override these settings, this method will insert a user document for you (if it doesn't already exist). To avoid this behavior, be sure to create the user document beforehand.verifyAuthCode({ phoneNumber: string, authCode: string }) : Promise<{ user: Object, authToken: string }>
user
document and a generated authToken
are returned.createAuthIndex(fieldOrSpec: string = 'phoneNumber', IndexOptions: object = { unique: true }): Promise<string>
createUsersIndex(fieldOrSpec: string = 'phoneNumber', IndexOptions: object = { unique: true }): Promise<string>
phoneNumber
for faster lookup and data integrity. See the MongoDB documentation for more info on fieldOrSpec
and options
.If you experience bugs, try upgrading to the latest version and checking the changelog. You can also post an issue on GitHub!
FAQs
Authentication using JSON web tokens, Mongo DB, and Twilio SMS
The npm package jwt-mongo-sms receives a total of 5 weekly downloads. As such, jwt-mongo-sms popularity was classified as not popular.
We found that jwt-mongo-sms demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.