{"componentChunkName":"component---src-templates-blog-list-template-js","path":"/131","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"excerpt":"You’re probably hosting your MongoDB on a reliable cloud service provider say Atlas for instance because you really want to focus on your…","fields":{"slug":"/engineering/self-hosted-mongo/"},"html":"

You’re probably hosting your MongoDB on a reliable cloud service provider say Atlas for instance because you really want to focus on your idea and delegate all the subtle key management areas such as networking, storage, access, etc.

\n

It all looks good initially until your small idea starts turning into a business and the cost starts skyrocketing. Even if that is not the case, this post will still give you a general overview of the technical complexities involved (and bucks saved!) if you were to migrate to a self-hosted solution.

\n

BTW, how much savings are we talking about? Let’s do a quick comparison between an Atlas instance and a self-hosted MongoDB on AWS.

\n

Atlas (~$166/month)

\n

\""Atlas\n$0.23/hour based on the above-selected requirements (~ cloud.mongodb.com)

\n



AWS (~$36/month)\n\""AWS

\n

$0.0416/hour for the instance and additional pricing based on the EBS type and storage (~ calculator.aws)

\n
\n

It is almost 4.5x savings just in terms of the infrastructure!

\n
\n

Now that you know the major why(s) and are still reading this post, without further ado, let’s dive into the tech.

\n
\n

Outline

\n
    \n
  1. Setting up the infrastructure
    2. \n
  2. Setting up MongoDB
    3. \n
  3. Bulk migration
    4. \n
  4. Delta-sync to bridge the connection switch latency (not applicable to stale clusters)
    5. \n
\n

Since the entire content can be a bit exhausting in one place, I’m going to divide this into 2 related posts.

\n

1. Setting up the Infrastructure

\n

I’m going to mention below the guide for setting up an instance running RedHat Enterprise Linux 8 on AWS. This is because MongoDB generally performs better with the xfs file-system.

\n

Spin up an EC2 Instance

\n

I’ve used a t3.small instance that comes with 2 vCPUs and 2Gb of RAM albeit you can select any instance of your choice.

\n
\n

It is recommended that your DB should have access to at least 1GB of RAM and 2 real cores as that directly affects the performance during caching & concurrency mechanisms as handled by the default engine WiredTiger. You can read more about the production notes related to the RAM and CPU requirements here.

\n
\n

Configuration Overview:

\n\n

I’m assuming that you’re familiar with creating a VM on AWS.

\n

Now, once the instance is in running state, assign an Elastic IP to it and then simply do a remote login into the machine.

\n
\n

We'll need the Elastic IP to setup public hostname for the instance

\n
\n
$ ssh -i <PEM_FILE> ec2-user@<ELASTIC_IP>
\n

Mount Additional Volumes

\n

We have added 2 additional EBS volumes other than the Root FS for Data and Logs which are yet to be mounted (Remember the 30Gb and 3Gb?). You can list the volume blocks using,

\n
$ sudo lsblk
\n

The additional volumes will be listed right after the root block (refer to the arrows)

\n

\""sudo

\n

In the image above, you can see that the additional volumes are named

\n
    \n
  1. xvdb (30Gb space to store data)
    2. \n
  2. xvdc (3Gb space to store logs)
    3. \n
\n

Now, let’s create the file-systems in those volumes.

\n
$ sudo mkfs.xfs -L mongodata /dev/xvdb\n$ sudo mkfs.xfs -L mongologs /dev/xvdc
\n
\n

-L is an alias option for setting the volume label

\n
\n

And then mount the volumes.

\n
$ sudo mount -t xfs /dev/xvdb /var/lib/mongo\n$ sudo mount -t xfs /dev/xvdc /var/log/mongodb
\n

In order for these changes to reflect, the system must be rebooted. Hence, now we also need the partition persistence so that in case of an unintentional reboot we don’t lose the Database storage.

\n

We can achieve this by specifying the mount rules in the fstab file. You can read more about it here.

\n

Before that let's copy the UUID of the above partitions(because they are unique and won't change over a system restart)

\n
$ sudo blkid
\n

\""sudo

\n

Copy the UUIDs listed for /dev/xvdb and /dev/xvdc. Refer to the “LABEL” for block identification

\n

Now open the /etc/fstab file and paste the configuration in the following format.

\n
UUID=<COPIED_UUID_FOR_DATA> /var/lib/mongo xfs defaults,nofail 0 0\nUUID=<COPIED_UUID_FOR_LOGS> /var/log/mongodb xfs defaults,nofail 0 0
\n

Update Hostname

\n

The hostname will be used to identify your database server on the network. You can either use the above assigned Elastic IP or Domain name (if available). Open the /etc/hostname file and append the entry. For e.g.

\n
ip-xx.us-east-2.compute.internal **<ELASTIC_IP> <DOMAIN_1> <DOMAIN_2>** ...
\n

Update the Process Limits (Optional)

\n

This is optionally required in order to control the maximum number of acceptable connections while keeping the system stable.\nOpen the /etc/security/limits.conf file and add the following entries.

\n
* soft nofile 64000\n* hard nofile 64000\n* soft nproc 32000\n* hard nproc 32000
\n

Now that all of the infra related prerequisites are sorted, reboot the instance, and let’s proceed to MongoDB installation.

\n
\n

1. Setting up MongoDB

\n

Add the Repo Source

\n

Create a file /etc/yum.repos.d/mongodb-org.4.2.repo and add the following package repository details.

\n
[mongodb-org-4.2]\nname=MongoDB Repository\nbaseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/4.2/x86_64/\ngpgcheck=1\nenabled=1\ngpgkey=https://www.mongodb.org/static/pgp/server-4.2.asc
\n

Now let’s install MongoDB.

\n
$ sudo yum -y install mongodb-org
\n

Create directories and setup permissions

\n

MongoDB by default uses the following paths to store the data and the internal logs:

\n
\n

/var/lib/mongo → Data
/var/log/mongodb → Logs

\n
\n

Create the directories

\n
$ sudo mkdir /var/lib/mongo\n$ sudo mkdir /var/log/mongodb
\n

Change user & group permissions

\n
$ sudo chown mongod:mongod /var/lib/mongo\n$ sudo chown mongod:mongod /var/log/mongod
\n

Create an Admin User

\n

The mongod daemon/service must be first running before we proceed to create a user.\nLet’s use the default config(stored in /etc/mongod.conf) for now and start the daemon process.

\n
$ sudo -u mongod mongod -f /etc/mongod.conf
\n

The above command will start the mongod daemon in fork mode (default).

\n

Now, let’s login to the server and create our first admin user.

\n

Open a mongo shell

\n
$ mongo
\n

Use the \"admin\" database to create the root-admin

\n
> use admin
\n

Create the admin user

\n
> db.createUser({user: "admin", pwd: "password", roles: [{role: "root", db: "admin"}]})
\n

Create a regular user

\n
> db.createUser({user: "normal_user", pwd: "password", roles: [{role: "readWriteAnyDatabase", db: "admin"}]})
\n

Shutdown the server for now. We'll restart again with the modified config

\n
> db.shutDownServer()
\n

Setting up Authentication

\n

Here, we’ll enable the database authentication and modify the bind-address for our server to be accessible in the public domain.\nOpen /etc/mongod.conf and make the below changes.

\n
# network interfaces\nnet:\n  port: 27017\n  bindIp: 0.0.0.0 # accessible on the network address\nsecurity:\n  authorization: enabled # creds will be required for making db operations
\n

Save the config and restart the server.

\n
$ sudo -u mongod mongod -f /etc/mongod.conf
\n

Test Login

\n

You can verify if the credentials work using,

\n
$ mongo -u admin -p password
\n

That is it about the initial setup! Please stay tuned for my next related post on the detailed migration process and tips on keeping the DB production-ready.

\n

P.S. Thanks to Piyush Kumar for helping curate this post!

\n","frontmatter":{"date":"June 30, 2020","updated_date":null,"description":"Learn how to optimize your DB cost? This article will help you with the complete migration steps from a cloud to a self-hosted environment.","title":"Self-Hosted MongoDB","tags":["MongoDB","Mongo","AWS","Atlas"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":2.0408163265306123,"src":"/static/1ded984fa0b8dec44a3794c8bf5b7b2e/58556/cover.webp","srcSet":"/static/1ded984fa0b8dec44a3794c8bf5b7b2e/61e93/cover.webp 200w,\n/static/1ded984fa0b8dec44a3794c8bf5b7b2e/1f5c5/cover.webp 400w,\n/static/1ded984fa0b8dec44a3794c8bf5b7b2e/58556/cover.webp 800w,\n/static/1ded984fa0b8dec44a3794c8bf5b7b2e/502a6/cover.webp 925w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Chinmaya Pati","github":"cnp96","avatar":null}}}},{"node":{"excerpt":"Roadmap of IDX-auto-tester We're delightfully Announcing the upcoming releases of LoginRadius Identity-Experience-Framework Open-Source…","fields":{"slug":"/engineering/roadmap-idx-autotester/"},"html":"

Roadmap of IDX-auto-tester

\n

We're delightfully Announcing the upcoming releases of LoginRadius Identity-Experience-Framework Open-Source Automation

\n

These full-version releases will include more test coverage and major changes with several improvements & code optimizations, the details have been given below.
\nThe below changes are planned to go live in multiple scheduled major releases starting with mid of June 2020.

\n

Release Roadmap:

\n

July 2020:

\n

Test Cases:

\n\n
\n

CI/CD pipelines for automation is to make everyday development tasks simple that can save time and reduce human intervention to check them every single code commit.

\n
\n

August 2020:

\n

Usability Improvements:

\n\n

Documentations:

\n\n
\n

We are not just delivering automation we deliver values to our customers, some useful tips \"to working with selenium and nightwatch\" can be expected with this release

\n
\n

September 2020:

\n

Code Level Improvements and Optimizations:

\n\n

Better Reporting:

\n\n
\n

Although current configuration does not support different browsers, still you can run on any browser by making few changes in nightwatch.json detailed guide is here

\n
\n

October 2020:

\n

Overcoming the Limitations:

\n\n

It is agreed that we are committed to delivering you a seamless experience in automation, but still, if you face any issue or need any enhancements, please report us here

\n\n","frontmatter":{"date":"June 30, 2020","updated_date":null,"description":null,"title":"Roadmap of idx-auto-tester","tags":["Automation","idx","roadmap"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/af8901a2791cbe7b9510d719854dd766/58556/roadmap_idx_auto_tester.webp","srcSet":"/static/af8901a2791cbe7b9510d719854dd766/61e93/roadmap_idx_auto_tester.webp 200w,\n/static/af8901a2791cbe7b9510d719854dd766/1f5c5/roadmap_idx_auto_tester.webp 400w,\n/static/af8901a2791cbe7b9510d719854dd766/58556/roadmap_idx_auto_tester.webp 800w,\n/static/af8901a2791cbe7b9510d719854dd766/99238/roadmap_idx_auto_tester.webp 1200w,\n/static/af8901a2791cbe7b9510d719854dd766/135cd/roadmap_idx_auto_tester.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Pareek","github":"rkpareek","avatar":null}}}},{"node":{"excerpt":"Today we will learn about the progressive web app, a very interesting and trending topic in current times, We will start with the basic…","fields":{"slug":"/engineering/build-pwa-using-vanilla-javascript/"},"html":"

Today we will learn about the progressive web app, a very interesting and trending topic in current times, We will start with the basic steps first on how Progressive Web App works with vanilla js. Also, we’ll cover the concept of PWAS without using any of the frameworks, it's just a plain vanillaJS.

\n

What are Progressive Web Apps?

\n

A Progressive Web app is an application which is built on top of HTML, JS and CSS with some extra features like service worker and manifest.json file. These extra features will give the ability to run the web application offline.

\n

Various big companies are moving towards the progressive web app instead of native apps, as it gives some much flexibility to end-users. In some websites you can find the + icon at the right side of the address bar, those are progressive web apps.

\n

Setup your base app for PWA

\n

We will be using npm to start our project, so firstly create a root folder using this command mkdir first-pwa-app or another name of your choice then go to that directory by using this command cd first-pwa-app. Run npm init

\n
npm init\n\npackage name: (first-pwa-app)\nversion: (1.0.0)\ndescription: This is the first PWA example\nentry point: (index.js): index.html\ntest command:\ngit repository:\nkeywords:\nauthor: Mohammed Modi\nlicense: (ISC)
\n

Once you fill up those details your final output of the package.json file will be below

\n
{\n  "name": "first-pwa-app",\n  "version": "1.0.0",\n  "description": "This is the first PWA example",\n  "main": "index.html",\n  "scripts": {\n    "test": "echo \\"Error: no test specified\\" && exit 1"\n  },\n  "author": "Mohammed Modi",\n  "license": "ISC"\n}
\n

After that, we need to install the serve dependency to serve the application in localhost so install it using npm npm i serve --save. And then add a script in the package.json file.

\n
{\n  ...\n  "scripts": {\n    "test": "echo \\"Error: no test specified\\" && exit 1",\n    "serve": "serve ."\n  },\n  ...\n}
\n

So finally our application is ready to serve in localhost. Now let's add some html and css

\n

Setting up the Javascript

\n

Create a directory for the app and add js, css, and images subdirectories. It should look like this when you’re finished:

\n
/first-pwa-app   # Project Folder\n    /css     # Stylesheets\n    /js      # Javascript\n    /images  # Image files.\n    package.json\n    package-lock.json\n    index.html\n    manifest.json\n    sw.js
\n

You will understand the use of manifest.json and sw.js files once we move ahead in this tutorial.

\n

Add Some code for app interface

\n

When writing the code for Progressive Web Application we need to keep in mind two requirements

\n
    \n
  1. The landing page should have some content even if the javascript is not loaded
    2. \n
  2. The App should be responsive and can be properly interactive in any device.
    3. \n
\n

For this app, to handle the first requirement we will add the static text in the Html page and for the second requirement, we will use the viewport.

\n

So let's add this code inside the index.html file.

\n
<!DOCTYPE html>\n<html lang="en">\n  <head>\n    <meta charset="utf-8" />\n    <title>My First PWA</title>\n    <link rel="stylesheet" href="css/style.css" />\n    <meta name="viewport" content="width=device-width, initial-scale=1.0" />\n  </head>\n  <body class="fullscreen">\n    <div class="container">\n      <h1 class="title">My First PWA!</h1>\n    </div>\n  </body>\n</html>
\n

Next, we need to create a file css/style.css and paste this code inside this

\n
body {\n  font-family: sans-serif;\n}\n\n/* Make content area fill the entire browser window */\n/* Make content area fill the entire browser window */\nhtml,\n.fullscreen {\n  display: flex;\n  height: 100%;\n  margin: 0;\n  padding: 0;\n  width: 100%;\n}\n\n/* Center the content in the browser window */\n.container {\n  margin: auto;\n}\n\n.title {\n  font-size: 3rem;\n}
\n

Once you add the code save all the files and run the script npm run serve which will start your application in http://localhost:5000/

\n

\"First

\n

Testing the App

\n

As we can see our application is running in the browser, let test it using the LightHouse Extension in Google Chrome browser. For the best result, I recommend testing in an incognito tab of google chrome.

\n

\"First

\n

As you can see we have green signals for both of our above requirement:

\n
    \n
  1. Has a tag with width or initial-scale
    2. \n
  2. Contains some content when JavaScript is not available
    3. \n
\n

But still, there is lots of work to do, so let's start with the first feature of PWA's.

\n

Adding a Web App Manifest

\n

Let's create a new file called manifest.json in the root of our application. To understand more about the manifest file check out [this doc]

\n
{\n  "name": "My First Progressive Web app",\n  "short_name": "First PWA",\n  "lang": "en-US",\n  "start_url": "/index.html",\n  "display": "standalone",\n  "background_color": "white",\n  "theme_color": "white"\n}
\n

Now update the index.html head tag by adding the manifest.json file as a link

\n
<head>\n  ...\n  <link rel="manifest" href="/manifest.json" />\n  ...\n</head>
\n

We should also declare the theme colour which should match with your manifest.json file as meta tag.

\n
<head>\n  ...\n  <meta name="theme-color" content="white" />\n  ...\n</head>
\n

Once you run the lighthouse test again you can see we got green signals in some points like

\n
    \n
  1. Sets a theme colour for the address bar.
    2. \n
\n

\"Improving

\n

App Icons

\n

Still, we need to add more attributes to our manifest.json files like icons so let's add the icons inside the images folder, I have used to icons pwa-icon-256.webp and pwa-icon-256.webp for this demo you can find in this repo. You can use various sizes in it. And finally, add the favicon.webp in the root of the project.

\n

So let's add the icons attribute after the short-name

\n
{\n  "name": "My First Progressive Web app",\n  "short_name": "First PWA",\n  "icons": [\n    {\n      "src": ".images/pwa-icon-256.webp",\n      "sizes": "256x256",\n      "type": "image/png"\n    },\n    {\n      "src": ".images/pwa-icon-512.webp",\n      "sizes": "512x512",\n      "type": "image/png"\n    }\n  ],\n  "lang": "en-US",\n  "start_url": "/index.html",\n  "display": "standalone",\n  "background_color": "white",\n  "theme_color": "white"\n}
\n

And the index.html will head can will look like

\n
<head>\n  ...\n  <link rel="apple-touch-icon" href="images/pwa-icon-256.webp" />\n  ...\n</head>
\n

You can also verify the manifest.json file by opening Chrome DevTools, in the Application Tab, the first tab in the sidebar manifest

\n

\"Application

\n

After running the test again, we can see all the manifest.json related issues are solved, The remaining issues can be resolved by adding the service worker.

\n

Adding Service Worker

\n

The next requirement of our app will be the service worker. The service worker is a script that runs in the background without any user interaction.

\n

The task of service worker will be to download and cache our content and then serve it when the user is offline. To understand more on service workers you can check this doc from mozilla.

\n

To integrate service workers we need to create a file called sw.js in the root of our project.

\n
\n

Note: Service worker will only have the access to the files of the current and sub-directories hence we need to place it in the root of our project

\n
\n
let cacheName = "my-first-pwa";\nlet filesToCache = ["/", "/index.html", "/css/style.css", "/js/main.js"];\n\n/* Start the service worker and cache all of the app's content */\nself.addEventListener("install", (e) => {\n  e.waitUntil(\n    caches.open(cacheName).then(function (cache) {\n      return cache.addAll(filesToCache);\n    })\n  );\n});\n\n/* Serve cached content when offline */\nself.addEventListener("fetch", (e) => {\n  e.respondWith(\n    caches.match(e.request).then((response) => {\n      return response || fetch(e.request);\n    })\n  );\n});
\n

The first 2 variables cacheName and filesToCache are used to create an offline cache in the browser. cacheName is used to create a cache of specific name and filesToCache will be the list of files that we need to cache, / will store the root files that is index.html even if the user does not specify the file name in the URL and then all other files specified in the array.

\n
\n

Note: Here I have used the filesToCache array as a list of static files just to demonstrate the purpose of PWA, it will stop working in production if even one file fails to load.

\n
\n

Finally, we will load our service worker, for that create js/main.js file and copy the below code.

\n
window.onload = () => {\n  "use strict";\n\n  if ("serviceWorker" in navigator) {\n    navigator.serviceWorker.register("./sw.js");\n  }\n};
\n

And add this script in the index.html file.

\n
...\n<script src="js/main.js"></script>
\n

So the final version of our index.html file will look like:

\n
<!DOCTYPE html>\n<html lang="en">\n  <head>\n    <meta charset="utf-8" />\n    <title>Hello World</title>\n    <link rel="apple-touch-icon" href="images/pwa-icon-256.webp" />\n    <link rel="stylesheet" href="css/style.css" />\n    <link rel="manifest" href="/manifest.json" />\n    <meta name="viewport" content="width=device-width, initial-scale=1.0" />\n    <meta name="theme-color" content="white" />\n  </head>\n  <body class="fullscreen">\n    <div class="container">\n      <h1 class="title">Hello World!</h1>\n    </div>\n    <script src="js/main.js"></script>\n  </body>\n</html>
\n

Now our application is made as fully PWA supported, you can verify it by running the lighthouse test.

\n

\"Full

\n

Finishing Up

\n

We are done with the code, now the last thing remaining in to host it in any of the https domain. As the PWA will be required to run in the secure domain.

\n

You can get the full source code of this example in this Github repo

\n

I hope you enjoyed the progressive web apps using vanilla js tutorial and found it useful. Please let me know what you think in the comments below.

\n","frontmatter":{"date":"June 26, 2020","updated_date":null,"description":"A simple step-by-step tutorial, all done with pure JavaScript, to set up a simple PWA that can be accessed offline using a web app manifest and a service worker.","title":"How to Build a PWA in Vanilla JS","tags":["PWA","JavaScript"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/59164c7de73786d49d2361d64689b1c7/58556/cover.webp","srcSet":"/static/59164c7de73786d49d2361d64689b1c7/61e93/cover.webp 200w,\n/static/59164c7de73786d49d2361d64689b1c7/1f5c5/cover.webp 400w,\n/static/59164c7de73786d49d2361d64689b1c7/58556/cover.webp 800w,\n/static/59164c7de73786d49d2361d64689b1c7/99238/cover.webp 1200w,\n/static/59164c7de73786d49d2361d64689b1c7/135cd/cover.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Mohammed Modi","github":"mohammed786","avatar":null}}}},{"node":{"excerpt":"In this blog, we’ll be implementing authentication with password hashing in a Node.js web application. For this, we’ll be using crypto, a…","fields":{"slug":"/engineering/password-hashing-with-nodejs/"},"html":"

In this blog, we’ll be implementing authentication with password hashing in a Node.js web application. For this, we’ll be using crypto, a package password hashing for Node.js.

\n

The Crypto module for Node JS helps developers to hash user passwords.

\n

Pre-requisites:

\n\n

Step 1. First, create a directory structure as below :

\n

hashApp

\n
--model\n----user.js\n--route\n----user.js\n--server.js
\n

Step 2. Create model/user.js file and add the following code :

\n
// Importing modules \nconst mongoose = require('mongoose'); \nvar crypto = require('crypto'); \n  \n// Creating user schema \nconst UserSchema = mongoose.Schema({ \n    name : { \n        type : String, \n        required : true\n    }, \n    email : { \n        type : String, \n        required : true\n    }, \n    hash : String, \n    salt : String \n}); \n  \n// Method to set salt and hash the password for a user \nUserSchema.methods.setPassword = function(password) { \n     \n // Creating a unique salt for a particular user \n    this.salt = crypto.randomBytes(16).toString('hex'); \n  \n    // Hashing user's salt and password with 1000 iterations, \n     \n    this.hash = crypto.pbkdf2Sync(password, this.salt,  \n    1000, 64, `sha512`).toString(`hex`); \n}; \n  \n// Method to check the entered password is correct or not \nUserSchema.methods.validPassword = function(password) { \n    var hash = crypto.pbkdf2Sync(password,  \n    this.salt, 1000, 64, `sha512`).toString(`hex`); \n    return this.hash === hash; \n}; \n  \n// Exporting module to allow it to be imported in other files \nconst User = module.exports = mongoose.model('User', UserSchema);
\n

Step 3. Create route/user.js file and add the following code:

\n
// Importing modules \nconst express = require('express'); \nconst router = express.Router(); \n\n// Importing User Schema \nconst User = require('../model/user'); \n\n// User login api \nrouter.post('/login', (req, res) => { \n\n    // Find user with requested email \n    User.findOne({ email : req.body.email }, function(err, user) { \n        if (user === null) { \n            return res.status(400).send({ \n                message : "User not found."\n            }); \n        } \n        else { \n            if (user.validPassword(req.body.password)) { \n                return res.status(201).send({ \n                    message : "User Logged In", \n                }) \n            } \n            else { \n                return res.status(400).send({ \n                    message : "Wrong Password"\n                }); \n            } \n        } \n    }); \n}); \n\n// User signup api \nrouter.post('/signup', (req, res, next) => { \n\n\n// Creating empty user object \n    let newUser = new User(); \n\n    // Initialize newUser object with request data \n    newUser.name = req.body.name, \n\n    newUser.email = req.body.email,\n\n\n    newUser.password=req.body.password\n\n                    // Call setPassword function to hash password \n                    newUser.setPassword(req.body.password); \n\n    // Save newUser object to database \n    newUser.save((err, User) => { \n        if (err) { \n            return res.status(400).send({ \n                message : "Failed to add user."\n            }); \n        } \n        else { \n            return res.status(201).send({ \n                message : "User added successfully."\n            }); \n        } \n    }); \n}); \n// Export module to allow it to be imported in other files \nmodule.exports = router;
\n

Step 4. Create server.js file :

\n
// Importing modules\nvar express = require('express');\nvar mongoose = require('mongoose');\nvar bodyparser = require('body-parser');\n  \n// Initialize express app\nvar app = express();\n  \n// Mongodb connection url\nvar MONGODB_URI = "mongodb://localhost:27017/hashAppDb";\n  \n// Connect to MongoDB\nmongoose.connect(MONGODB_URI);\nmongoose.connection.on('connected', () => {\n    console.log('Connected to MongoDB @ 27017');\n});\n  \n// Using bodyparser to parse json data\napp.use(bodyparser.json());\n  \n// Importing routes\nconst user = require('./route/user');\n  \n// Use user route when url matches /api/user/\napp.use('/api/user', user);\n  \n// Creating server\nconst port = 3000;\napp.listen(port, () => {\n    console.log("Server ru\nnning at port: " + port);\n});
\n

Step 5. Run server.js file using command

\n
node server.js
\n

Step 6. Open Postman and create a post request to localhost:3000/api/user/signup with following body parameter:

\n
{\n"name" : "test".\n"email" : "test@test.com",\n"password" : "test1234"\n}
\n

Run the request and you will get a success response:

\n
{\n"message" : "user added sucessfully"\n}
\n

User data is stored in the database as below:

\n
    "_id": {\n        "$oid": "5ab71ef2afb6db0148052f6f"\n    },\n    "name": "test",\n    "email": "test@test.com",\n    "salt": "ddee18ef6a6804fbb919b25f790005e3",\n    "hash": "bbf13ae4db87d475ca0ee5f97e397248a23509fc10c82f1e3cf110\n     b352c3ca6cc057955ace9d541573929cd7a74a280a02e8cb549136b43df7704caaa555b38a",\n    "__v": 0\n}
\n

If we have sensitive data or information that you need to be protected, ensuring it is secured correctly is important. With the above process, we can now successfully store our hashed password into our database with a bit of additional security.

\n

You can check the code on Github.

\n","frontmatter":{"date":"June 25, 2020","updated_date":null,"description":null,"title":"Password hashing with NodeJS","tags":["Security","NodeJs"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.4598540145985401,"src":"/static/7c5686f355f37377e26ec91cbaa6cbed/58556/cover.webp","srcSet":"/static/7c5686f355f37377e26ec91cbaa6cbed/61e93/cover.webp 200w,\n/static/7c5686f355f37377e26ec91cbaa6cbed/1f5c5/cover.webp 400w,\n/static/7c5686f355f37377e26ec91cbaa6cbed/58556/cover.webp 800w,\n/static/7c5686f355f37377e26ec91cbaa6cbed/99238/cover.webp 1200w,\n/static/7c5686f355f37377e26ec91cbaa6cbed/ba24a/cover.webp 1440w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Ashish Sharma","github":"ashish8947","avatar":null}}}},{"node":{"excerpt":"The online gambling industry is one of the potential sectors that may make it through the pandemic with the least possible damage. In fact…","fields":{"slug":"/identity/online-casino-and-gambling-cyber-threat/"},"html":"

The online gambling industry is one of the potential sectors that may make it through the pandemic with the least possible damage. In fact, according to a study by the GrandViewResearch, online gambling is about to witness massive growth, and in the US alone, it will reach a value of $102.9 billion by 2025.

\n

No wonder the online gambling ecosystem is at its finest phase!

\n

With the COVID-19 situation confining people to their homes, there's a lot more population playing on the internet. They have even outperformed their physical counterparts by massive numbers.

\n

In an environment where gambling occurs online, thousands of billions of casino money are transacted via credit and debit cards, wire transfers, and e-wallets. It is no surprise that gambling companies are one of the most favorable targets for scammers and hackers.

\n

Cybercriminals target their resources in two major ways: one they steal the obvious - money and the other they look for confidential data shared by gamblers online.

\n

Needless-to-say, the online gambling industry, therefore, needs to take the necessary steps to build safe and secure platforms for casino operators and consumers at large.

\n

Online Casino, a Multi-Billion Dollar Industry- What's About to Change

\n

The online gambling industry has undergone various changes over the past decades and is simultaneously expected to exhibit numerous transformations in the years to come. 

\n

For example, the online gambling market is expected to grow at a compound annual growth rate (CAGR) of 11.5% from 2020 to 2027. That's huge!

\n

\n

Source: www.grandviewresearch.com

\n

This also means almost every player in the industry will compete to sustain in the competition, software developers will create more innovative games, and casinos will incorporate new ideas to improve customer experience. So, what are these new ideas? 

\n

Here are five key trends that could change the entire casino and gambling landscape.

\n

1. Rise of Cryptocurrency Transactions in Casinos

\n

Cryptocurrencies are no longer the future. The majority of online gambling and casino operators have already switched to Bitcoin and other cryptocurrencies as their standard mode of payment. Clearly, they see many advantages. Some of which include:

\n\n

2. Adoption of AR and VR in Casinos

\n

Virtual reality (VR) is another dimension that has been working its way into the gaming industry - with many casinos already integrating it into their environment.

\n

What this technology does is it designs an entirely new environment, a whole new reality. An example of this is poker, where multiple players share one environment, adding to the experience.

\n

Similar to virtual reality, there is another technology called augmented reality (AR). Unlike VR, however, AR supplements the current environment with computer overlays. Heard of Pokémon Go? It uses AR, and now it is gearing up to enter the gambling industry.

\n

Considering that this technology improves an already established environment, live gaming is expected to become even more captivating.

\n

3. Customer's Evolving Gambling Habits

\n

It is no brainer that the customer's habit evolves with time. Social gambling and the rising popularity of gambling applications are some of the biggest indicators in this regard. Players can now easily compete on leaderboards and participate in social slots, whenever they want to.

\n

Mobile technology has been a massive influence on people with a huge percentage of the world's population owning a smartphone. Casinos are more than ever investing in gaming applications and creating mobile-friendly games. It seems like mobile games will soon take over their desktop competition.

\n

\n

Source: www.grandviewresearch.com

\n

4. Stricter Casinos & Gambling Regulations

\n

The world is getting pretty serious about gambling. Some countries have already legalized online gambling, while others are looking forward to making a move in 2020. 

\n

For example, Belarus legalized online casinos in 2019, Ukraine introduced a bill to legalize gaming. Russia has simplified the identification procedure required in betting, and even the UK accepted the obligatory requirements related to customer identification. 

\n

5. Evolution of Live Casinos

\n

Another milestone in online gambling is probably the rapid evolution of live casinos. Games are carried out by dealers with professional lighting and sound equipment from exclusive studios. 

\n

Then, cameras are mounted at various room angles, so players can witness everything that's happening inside the studio. Going forward, the concept of a live casino will gain even more popularity.

\n

Why Is Online Gambling and Casino Security So Crucial

\n

In 2020, reducing the effects of cyber attacks and online fraud is crucial to sustaining the online gambling industry. Hackers are becoming extremely advanced, using tools and implementing sophisticated techniques like signal manipulation through fake apps and app-based hacking to breach data and break down online security protocols.

\n

Besides, Statista.com estimates that the global online gambling market will be valued at more than $94 billion USD in 2024 - meaning more the figure, more the risk of cybercrime.

\n

\n

Source: statista

\n

More than ever now is the time when cyber protection will play a critical role in the continued development and success of this revolutionary online gambling industry.

\n

Recent Cyber Attacks in Online Gambling Sites

\n

The primary threat to cybersecurity that online casinos face is hacking. It may include targeted attacks forcing servers to get swamped with bot traffic, or it may consist of more sophisticated tactics designed to gain access to confidential customer data. 

\n

Here are a few instances of recent breaches that will help you understand its severity in today's online gambling threat landscape. 

\n\n

Types of Attacks on Online Casino, Betting and Gambling Sites 

\n

\"online

\n

Online gambling and casino sites face security threats from several sources. For starters, some external hackers launch attacks to commit fraud from the comfort of their home or anywhere (for that matter). Next, some insiders hold administrative positions inside the business itself and steal customer details. 

\n

Anyway, let's understand some of the major types of cyberattacks impacting the gambling industry. 

\n

Expediting 

\n

Expediting gameplay abuse is not new to the casino and online gambling industry. It is an automated threat that utilizes bots to speed up time-consuming actions, mostly to offer unfair advantages to players by violating rules in the gameplay. 

\n

Expediting attacks decline user appeal, result in loss of subscription revenue, and may even risk your reputation as an online game service provider.

\n

DDoS Attack

\n

In Distributed Denial of Service (DDoS) attacks, hackers flood gambling sites with an unexpected surge of traffic, leading to insignificant delays in loading times or completely crashing your website. 

\n

Most naturally, players lose interest in the gambling company and jump off to their competitors.

\n

Scraping 

\n

Scraping is another automated attack where hackers use bots to steal data from APIs, websites, and databases and consequently use those to exploit gambling operations. 

\n

Scrapers often lead to increased risk of latency on gambling sites using excessive bandwidth with their requests, making legitimate customers suffer from long load times.

\n

Account Takeover Attacks

\n

Account takeover attack is a complex challenge for the online gambling industry. Hackers gain illegal access to a genuine user profile to perform payment or identity fraud. 

\n

In the gambling space, they steal players' resources and sell them on the dark market. They lure victims into accepting malicious friend requesting or by clicking on infected links. 

\n

SQL Injection 

\n

A Structured Query Language (SQL) injection attack happens when a hacker feeds infected SQL statements to take over the database server and add, modify, or delete data according to their will. 

\n

By breaking into application security measures, hackers can easily pass through validation and approval checkpoints. This method of attack is mostly used by attackers to gain access over personal data, intellectual properties of gamblers, customer information, gaming secrets, and more.

\n

How LoginRadius Can Enhance the Experience of Online Gaming With Advance Security

\n

\"How

\n

LoginRadius is a powerful customer identity and access management (CIAM) platform that protects online gamblers' identity and prevents even the most sophisticated bots from infecting the gaming provider. It detects and blocks automated threats, including expediting, scraping, account takeover, DDoS, and more.

\n

Here's how the LoginRadius platform protects the gaming industry from malicious bot attacks and significantly improving customer experience.

\n\n

\"adaptive-mfa\"

\n\n

Conclusion

\n

Adhering to the COVID situation and keeping social distancing in mind, more and more people are turning to the multi-billion dollar gambling industry to find solace. Protecting online casinos, betting, and gambling site from malicious bots is a big deal. 

\n

With the ongoing pandemic situation, gambling providers should primarily focus on ensuring that gambling is fair, crime-free, and protects minors. A CIAM platform can help you tap all these touchpoints.

\n

\"book-free-demo-loginradius\"

\n","frontmatter":{"date":"June 25, 2020","updated_date":null,"description":"The online gambling industry, needs to take the necessary steps to build safe and secure platforms for casino operators and consumers.","title":"Online Casino and Gambling Industry Is Gaining Momentum, So Is the Cyber Threat","tags":["security"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.408450704225352,"src":"/static/19bf37c964e8bdffca34c56ef5ff6584/c0524/Online-Casino-and-Gambling-Industry.webp","srcSet":"/static/19bf37c964e8bdffca34c56ef5ff6584/61e93/Online-Casino-and-Gambling-Industry.webp 200w,\n/static/19bf37c964e8bdffca34c56ef5ff6584/1f5c5/Online-Casino-and-Gambling-Industry.webp 400w,\n/static/19bf37c964e8bdffca34c56ef5ff6584/c0524/Online-Casino-and-Gambling-Industry.webp 769w","sizes":"(max-width: 769px) 100vw, 769px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.webp"}}}},{"node":{"excerpt":"Idx-Auto-Tester is LoginRadius Identify Experience Automation Framework which refers to IEF Automation, is an open-source automation…","fields":{"slug":"/engineering/introduction-of-idx-auto-tester/"},"html":"

Idx-Auto-Tester is LoginRadius Identify Experience Automation Framework which refers to IEF Automation, is an open-source automation framework built-in Nightwatch| Node.js tool with delivering all the standard authentication cases of LoginRadius Identity Experience.\nThis automation framework has been created for The LoginRadius Identity Experience Framework which is a ready-to-use solution that provides predefined layouts for all necessary authentication actions. It has all of the user accounts flows available, such as login, registration, forgotten password, and profile management.

\n

Technology used to create Idx-Auto-Tester

\n

We used Nightwatch.js end-to-end testing framework to create our Idx-Auto-Tester. This framework relies on Selenium and provides several commands and assertions within the framework to perform operations on DOM elements. It internally uses the powerful W3C Webdriver API or the Selenium Webdriver and simplifies writing end-to-end automated tests in Node.js and effortlessly sets up for Continuous Integration.

\n

Nightwatch uses JavaScript language (Node.js) and CSS/XPath to identify an element. It has Built-in command-line test runner which can run the tests either sequentially or in parallel, together, by group, tags, or by single.

\n

Installation

\n

Step 1: Download and Install Java.

\n

Step 2: Install Node.js.

\n

Step 3: Install Nightwatch. In the command line, navigate to any directory and type

\n
  npm install -g nightwatch (here ‘g’ is for installing globally).
\n

Step 4: Create a folder structure as shown below where Project is the root.

\n

\n

Step 5. Now it is required to install selenium-server-standalone.jar and chromedriver.exe along with other dependencies to execute test cases.

\n

As all the dependencies are added in nightwatch.json, so by executing below command, these will be added in node_modules folder

\n
  npm install
\n

Configuring and Setting up Nightwatch.js

\n

Now we have installed all the dependencies and configuration setup for the automation framework. Nightwatch.js offers an in-built test runner which expects a JSON configuration file to be passed. The default configuration file is nightwatch.json which should be present in the project’s root directory.

\n

Step 6. In the root folder, create “nightwatch.js” file and place the following line:

\n
require("nightwatch/bin/runner.js")
\n

Step 7. Now create nightwatch.json configuration file with the configurations mentioned as below code snippet for testing with Selenium and JavaScript.

\n
{\n  "src_folders": ["test"],\n  "output_folder": "tests_output",\n  "custom_commands_path": "helpers/custom-commands",\n  "custom_assertions_path": "",\n  "page_objects_path": "",\n  "globals_path": "",\n  "test_workers": {\n    "enabled": false,\n    "workers": 3\n  },\n\n  "selenium": {\n    "start_process": true,\n    "server_path": "node_modules/selenium-server-standalone-jar/jar/selenium-server-standalone-3.13.0.jar",\n    "log_path": "",\n    "host": "127.0.0.1",\n    "port": 4444,\n    "cli_args": {\n      "webdriver.chrome.driver": "node_modules/chromedriver/lib/chromedriver/chromedriver.exe",\n      "webdriver.ie.driver": ""\n    }\n  },\n\n  "test_settings": {\n    "default": {\n      "skip_testcases_on_fail": false,\n      "launch_url": "http://localhost",\n      "selenium_port": 4444,\n      "selenium_host": "127.0.0.1",\n      "silent": true,\n      "screenshots": {\n        "enabled": true,\n        "path": "screenshots"\n      },\n      "desiredCapabilities": {\n        "browserName": "chrome",\n        "javascriptEnabled": false,\n        "acceptSslCerts": false,\n        "chromeOptions": {\n          "args": ["--headless-none"]\n        }\n      }\n    },\n    "firefox": {\n      "desiredCapabilities": {\n        "browserName": "firefox",\n        "javascriptEnabled": true,\n        "acceptSslCerts": true,\n        "cli_args": {\n          "globals": {\n            "env": "fire  fox"\n          }\n        }\n      }\n    },\n\n    "ie": {\n      "desiredCapabilities": {\n        "browserName": "internet explorer",\n        "javascriptEnabled": true,\n        "acceptSslCerts": true,\n        "cli_args": {\n          "globals": {\n            "env": "ie"\n          }\n        }\n      }\n    }\n  }\n}
\n

Step 8. Now its time to design test case of any scenario, same as created in our Idx-Auto-Tester Framework under test folder named as TC01UserLogin

\n

To create functions/methods, we used nightwatch custom commands approach to create commands for all the required functions under custom-commands folder, like as there is command created for createUser.js which used to create the user and call it under test case.

\n
\n

Note: We are using 'Function-style commands' of Nightwatch to create command to resolve the asynchronous queueing system problem while running the test case.

\n
\n

Step 9. The final thing we are required to do is to execute the tests from the base directory of the project using the command:

\n
npm test
\n
\n

Important Tip : A script has been added in package.json to define test execution command:

\n
\n
"scripts":\n  {\n    "test": "node nightwatch.js --reporter html-reporter.js test"\n    }
\n

This command will validate the tests and dependencies and then execute the test suite, which will open up the mentioned browser and execute the desired test steps.

\n

Parallel Testing with Nightwatch.js in Selenium WebDriver

\n

It is required to update the configuration to execute the tests in parallel by enabling the test_workers as true. This will enable parallel execution and execute all tests on a defined number of workers.

\n
  "test_workers": {\n    "enabled": true,\n    "workers": 3\n  },
\n

This is all about Idx-Auto-Tester Framework Implementation

\n

In this framework design, we have covered various flows of LoginRadius Identity Experience Automation testing with Selenium Javascript. I hope we are now clear about the approach for an end-to-end automation testing with Selenium JavaScript using Nightwatch.js with the reference of Idx-Auto-Tester. We are aware of all the prerequisites required for setting up Nightwatch.js. It automates the entire test suite quickly with minimal configuration and is readable as well as easy to update. Our framework is also capable to use the best feature provided by Nightwatch.js framework which is the parallel testing of cases that proves to be time-efficient. The test results can directly be read from the terminal and also stored at a specified output folder.

\n","frontmatter":{"date":"June 22, 2020","updated_date":null,"description":null,"title":"Introduction of Idx-Auto-Tester","tags":["Automation","Idx-Auto-Tester"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/4cce23ed76b3e769d45c63bf586f8166/58556/idx-auto-tester.webp","srcSet":"/static/4cce23ed76b3e769d45c63bf586f8166/61e93/idx-auto-tester.webp 200w,\n/static/4cce23ed76b3e769d45c63bf586f8166/1f5c5/idx-auto-tester.webp 400w,\n/static/4cce23ed76b3e769d45c63bf586f8166/58556/idx-auto-tester.webp 800w,\n/static/4cce23ed76b3e769d45c63bf586f8166/99238/idx-auto-tester.webp 1200w,\n/static/4cce23ed76b3e769d45c63bf586f8166/135cd/idx-auto-tester.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Himanshi Sharma","github":"Himanshi0512","avatar":null}}}}]},"markdownRemark":{"excerpt":"Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards…","fields":{"slug":"/identity/developer-first-identity-provider-loginradius/"},"html":"

Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards and refining approaches to building secure, seamless experiences.

\n

We’re here to support developers on that journey. We know how important simplicity, efficiency, and well-structured documentation are when working with identity and access management solutions. That’s why we’ve redesigned the LoginRadius website—to be faster, more intuitive, and developer-first in every way.

\n

The goal? Having them spend less time searching and more time building.

\n

What’s New and Improved on the LoginRadius Website?

\n

LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.

\n

Here’s a closer look at what’s new and why it’s important:

\n

A Developer-Friendly Dark Theme

\n

\"This

\n

Developers spend long hours working in dark-themed IDEs and terminals, so we’ve designed the LoginRadius experience to be developer-friendly and align with that preference.

\n

The new dark mode reduces eye strain, enhances readability, and provides a seamless transition between a coding environment and our platform. Our new design features a clean, modern aesthetic with a consistent color scheme and Barlow typography, ensuring better readability. High-quality graphics and icons are thoughtfully placed to enhance the content without adding visual clutter.

\n

So, whether you’re navigating our API docs or configuring authentication into your system, our improved interface will make those extended development hours more comfortable and efficient.

\n

Clear Categorization for LoginRadius Capabilities

\n

\"This

\n

We’ve restructured our website to provide a straightforward breakdown of our customer identity and access management platform capabilities, helping you quickly find what you need:

\n\n

This structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.

\n

Developer-First Navigation

\n

\"This

\n

We’ve been analyzing developer workflows to identify how you access key resources. That’s why we redesigned our navigation with one goal in mind: to reduce clicks and make essential resources readily available.

\n

The new LoginRadius structure puts APIs, SDKs, and integration guides right at the menu bar under the Developers dropdown so you can get started faster. Our Products, Solutions, and Customer Services are also clearly categorized, helping development teams quickly find the right tools and make informed decisions.

\n

Quick Understanding of Integration Benefits

\n

\"This

\n

Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.

\n

Our platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.

\n

Over to You Now!

\n

Check out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.

\n

Do not forget to explore the improved navigation and API documentation, and get started with our free trial today. We’re excited to see what you’ll build with LoginRadius!

\n","frontmatter":{"date":"February 21, 2025","updated_date":null,"description":"LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve redesigned our website interface, making navigation more intuitive and reassuring that essential resources are easily accessible.","title":"Revamped & Ready: Introducing the New Developer-First LoginRadius Website","tags":["Developer tools","API","Identity Management","User Authentication"],"pinned":true,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp","srcSet":"/static/80b4e4fbe176a10a327d273504607f32/61e93/hero-section.webp 200w,\n/static/80b4e4fbe176a10a327d273504607f32/1f5c5/hero-section.webp 400w,\n/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp 800w,\n/static/80b4e4fbe176a10a327d273504607f32/99238/hero-section.webp 1200w,\n/static/80b4e4fbe176a10a327d273504607f32/7c22d/hero-section.webp 1600w,\n/static/80b4e4fbe176a10a327d273504607f32/1258b/hero-section.webp 2732w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.webp"}}}},"pageContext":{"limit":6,"skip":780,"currentPage":131,"type":"///","numPages":164,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}