{"componentChunkName":"component---src-templates-blog-list-template-js","path":"/engineering/36","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"excerpt":"In this blog, we’ll be implementing authentication via Google in a Go web application. For this, we’ll be using Goth - Multi-Provider…","fields":{"slug":"/engineering/google-authentication-with-golang-and-goth/"},"html":"

In this blog, we’ll be implementing authentication via Google in a Go web application. For this, we’ll be using Goth - Multi-Provider Authentication Package for Go

\n

Before You Get Started

\n

This tutorial assumes you have:

\n\n

Step 1: Create a Google client ID and client secret

\n

We can create a client ID and client secret using its Google API Console. You need to follow below steps once you open Google API Console

\n\n

Note: If Google doesn't support http://localhost:3000, then use http://127.0.0.1:3000

\n

Step 2: Initialize a Go project using Go modules

\n

First in an empty folder run the below command

\n
go mod init googleauth
\n

go mod init creates a new go.mod file and automatically imports dependencies when you will run go program

\n

Step 3: Writing golang server code to accept web requests

\n

Create a file main.go in the root folder of your app and add the following code:

\n

A small description for packages used in below code

\n\n
package main\n\nimport (\n  "fmt"\n  "html/template"\n  "net/http"\n  \n\n  "log"\n\n  "github.com/gorilla/pat"\n  "github.com/markbates/goth"\n  "github.com/markbates/goth/gothic"\n  "github.com/markbates/goth/providers/google"\n  "github.com/gorilla/sessions"\n)\n\n\nfunc main() {\n  \n  key := "Secret-session-key"  // Replace with your SESSION_SECRET or similar\n  maxAge := 86400 * 30  // 30 days\n  isProd := false       // Set to true when serving over https\n\n  store := sessions.NewCookieStore([]byte(key))\n  store.MaxAge(maxAge)\n  store.Options.Path = "/"\n  store.Options.HttpOnly = true   // HttpOnly should always be enabled\n  store.Options.Secure = isProd\n\n  gothic.Store = store\n\n  goth.UseProviders(\n    google.New("our-google-client-id", "our-google-client-secret", "http://localhost:3000/auth/google/callback", "email", "profile"),\n  )\n\n  p := pat.New()\n  p.Get("/auth/{provider}/callback", func(res http.ResponseWriter, req *http.Request) {\n\n    user, err := gothic.CompleteUserAuth(res, req)\n    if err != nil {\n      fmt.Fprintln(res, err)\n      return\n    }\n    t, _ := template.ParseFiles("templates/success.html")\n    t.Execute(res, user)\n  })\n\n  p.Get("/auth/{provider}", func(res http.ResponseWriter, req *http.Request) {\n    gothic.BeginAuthHandler(res, req)\n  })\n\n  p.Get("/", func(res http.ResponseWriter, req *http.Request) {\n    t, _ := template.ParseFiles("templates/index.html")\n    t.Execute(res, false)\n  })\n  log.Println("listening on localhost:3000")\n  log.Fatal(http.ListenAndServe(":3000", p))\n}
\n

Note: The callback URL in google.New should be the same as used in the google app configuration.

\n

If it is hard to understand the code, Here is the description of all the routes used in the code mentioned above

\n\n

Step 4: Creating a Login and Profile page

\n

Create an html file under path templates/index.html, it will render into a nice looking social login page:

\n
<!-- templates/index.html -->\n<!doctype html>\n<html>\n<head>\n    <title>Google SignIn</title>\n    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"> <!-- load bulma css -->\n    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css"> <!-- load fontawesome -->\n    <style>\n        body        { padding-top:70px; }\n    </style>\n</head>\n<body>\n<div class="container">\n    <div class="jumbotron text-center text-success">\n        <h1><span class="fa fa-lock"></span> Social Authentication</h1>\n        <p>Login or Register with:</p>\n        <a href="/auth/google" class="btn btn-danger"><span class="fa fa-google"></span> SignIn with Google</a>\n    </div>\n</div>\n</body>\n</html>
\n

After it we will create an Html file under path templates/success.html, it will be used to show the user profile information we will get after authenticated by google

\n
<!-- templates/success.html -->\n<!doctype html>\n<html>\n  <head>\n    <title>Google SignIn</title>\n    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"> <!-- load bulma css -->\n    <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css"> <!-- load fontawesome -->\n      <style>\n          body        { padding-top:70px; }\n      </style>\n  </head>\n  <body>\n    <div class="container">\n      <div class="jumbotron">\n          <h1 class="text-success  text-center"><span class="fa fa-user"></span> Profile Information</h1>\n          <div class="row">\n            <div class="col-sm-6">\n                <div class="well">\n                        <p>\n                            <strong>Id</strong>: {{.UserID}}<br>\n                            <strong>Email</strong>: {{.Email}}<br>\n                            <strong>Name</strong>: {{.Name}}\n                        </p>\n                </div>\n            </div>\n        </div>\n      </div>\n    </div>\n  </body>\n</html>
\n

Note: Here we are also using bootstrap and font-awesome css to make our web pages look good.

\n

We have finished building our social login page, let's run the application by below command

\n
go run main.go
\n

Once our server is running, we can see our social login page on http://localhost:3000/

\n

\"Social

\n

We need to click on SignIn with Google button, which will redirect us to the google login page.

\n

\"Google

\n

After login with our google credentials, it will redirect back to our application and on the success page, we can see the details of the logged-in user and can save this detail in a database for future use also.

\n

\"Social

\n

As we have seen it is fairly easy to build a google social authentication system with Go language and Goth package, You can found the complete code used in this tutorial on our Github Repo

\n","frontmatter":{"date":"June 11, 2020","updated_date":null,"description":"Learn how to implement Google OAuth2 Authentication in Golang using Goath","title":"Google OAuth2 Authentication in Golang","tags":["Go","SocialLogin","Oauth"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.6666666666666667,"src":"/static/5960f981e6b283300239a1ecf91728b0/e9589/google_golang.webp","srcSet":"/static/5960f981e6b283300239a1ecf91728b0/61e93/google_golang.webp 200w,\n/static/5960f981e6b283300239a1ecf91728b0/1f5c5/google_golang.webp 400w,\n/static/5960f981e6b283300239a1ecf91728b0/e9589/google_golang.webp 500w","sizes":"(max-width: 500px) 100vw, 500px"}}},"author":{"id":"Puneet Singh","github":"puneetsingh24","avatar":null}}}},{"node":{"excerpt":"This blog article will guide you to add \"log in with LinkedIn\"\nfunctionality in your application. Here we will be implementing Linkedin…","fields":{"slug":"/engineering/linkedin-login-using-node-passport/"},"html":"

This blog article will guide you to add \"log in with LinkedIn\"\nfunctionality in your application. Here we will be implementing Linkedin Login using NodeJS and Passport.

\n

Passport is an authentication middleware for Node, which authenticates requests and delegates all other functionality to the application. Considering the unique application requirements, Passport has stuck to authentication mechanisms known as strategies. In the blog, we will be implementing a similar strategy for Login with Linkedin.

\n

Pre -Requisites:

\n
    \n
  1. Basic Knowledge of NodeJS
    2. \n
  2. Node JS should be installed on your system.
    3. \n
\n

Steps to configure

\n
    \n
  1. Creating Linkedin APP_ID and APP_SECRET
    2. \n
  2. Go to Developer Linkedin and login with your Linkedin account.
    3. \n
  3. Once you have registered, click on the create app link and add the required details to create an app
    4. \n
\n

\"Create

\n

Provide basic details about your app:

\n\n
  cd Linkedin-node-authentication
\n
    \n
  1. In the root create a file package.json and copy the following code
    2. \n
\n

The dependencies, we are going to use in the projects are

\n\n
{\n  "name": "linkedin-login-node",\n  "version": "1.0.0",\n  "description": "Basic application for setting up Linkedin login using node and passport",\n  "main": "index.js",\n  "scripts": {\n    "test": "echo \\"Error: no test specified\\" && exit 1",\n    "start": "node server.js"\n  },\n  "author": "LoginRadius",\n  "license": "ISC",\n  "dependencies": {\n    "ejs": "^3.1.2",\n    "express": "^4.17.1",\n    "express-session": "^1.17.1",\n    "passport": "^0.4.1",\n    "passport-linkedin-oauth2": "^2.0.0"\n  }\n}
\n
    \n
  1. \n

    After this run the following command in the terminal

    \n
    npm install
    \n
    2. \n
  2. Now create a file named server.js and paste the following code
    3. \n
\n
const express = require('express');\nconst app = express();\nconst session = require('express-session');\nconst passport = require('passport');\nconst LinkedInStrategy = require('passport-linkedin-oauth2').Strategy;\nconst routes = require('./routes.js');\nconst config = require('./config')\n\napp.set('view engine', 'ejs');\n\napp.use(session({\n  resave: false,\n  saveUninitialized: true,\n  secret: 'SECRET'\n}));\n\napp.use(passport.initialize());\napp.use(passport.session());\n\npassport.serializeUser(function (user, cb) {\n  cb(null, user);\n});\n\npassport.deserializeUser(function (obj, cb) {\n  cb(null, obj);\n});\n\npassport.use(new LinkedInStrategy({\n  clientID: config.linkedinAuth.clientID,\n  clientSecret: config.linkedinAuth.clientSecret,\n  callbackURL: config.linkedinAuth.callbackURL,\n  scope: ['r_emailaddress', 'r_liteprofile'],\n}, function (token, tokenSecret, profile, done) {\n  return done(null, profile);\n}\n));\n\napp.use('/', routes);\n\nconst port = 3000;\n\napp.listen(port, () => {\n  console.log('App listening on port ' + port);\n});
\n
    \n
  1. Now create a file named routes.js in the root directory and paste the following code
    2. \n
\n
const passport = require('passport');\nconst express = require('express');\nvar router = express.Router();\n\nrouter.get('/', function (req, res) {\n  res.render('pages/index.ejs'); // load the index.ejs file\n});\n\nrouter.get('/profile', isLoggedIn, function (req, res) {\n  res.render('pages/profile.ejs', {\n    user: req.user // get the user out of session and pass to template\n  });\n});\n\nrouter.get('/auth/linkedin', passport.authenticate('linkedin', {\n  scope: ['r_emailaddress', 'r_liteprofile'],\n}));\n\nrouter.get('/auth/linkedin/callback',\n  passport.authenticate('linkedin', {\n    successRedirect: '/profile',\n    failureRedirect: '/login'\n  }));\n\nrouter.get('/logout', function (req, res) {\n  req.logout();\n  res.redirect('/');\n});\n\n\nfunction isLoggedIn(req, res, next) {\n  if (req.isAuthenticated())\n    return next();\n  res.redirect('/');\n}\n\nmodule.exports = router;
\n
    \n
  1. Create a directory views and under this create a directory named pages. Under this folder create two pages named profile.ejs and index.ejs
    2. \n
\n
// index.ejs\n<!doctype html>\n<html>\n\n<head>\n  <title>Linkedin Node Authentication</title>\n  <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">\n  <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">\n  <link rel="stylesheet" type="text/css"\n    href="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.5/css/materialize.min.css">\n  <style>\n    .linkedin {\n      background-color: #0073b1 !important;\n      color: #fff !important;\n    }\n    .fa-linkedin-f:before,\n    .fa-linkedin:before {\n      content: "\\f0e1";\n    }\n  </style>\n</head>\n\n<body>\n  <nav class="light-blue lighten-1" role="navigation">\n    <div class="nav-wrapper container">\n      <a id="logo-container" href="#" class="brand-logo">Node Authentication</a>\n    </div>\n  </nav>\n  <div class="section no-pad-bot" id="index-banner">\n    <div class="container">\n      <br><br>\n      <div class="row center">\n        <div class="col s6 offset-s3">\n          <div class="card">\n            <div class="card-content">\n              <span class="card-title">Linkedin Login using Node and passport</span>\n            </div>\n            <div class="card-action">\n              <a href="/auth/linkedin" class="waves-effect waves-light btn social linkedin">\n                <i class="fa fa-linkedin"></i> Sign in with Linkedin\n              </a>\n            </div>\n          </div>\n        </div>\n      </div>\n    </div>\n  </div>\n</body>\n\n</html>
\n
<!- profile.ejs->\n<!doctype html>\n<html>\n\n<head>  \n  <title>LinkedIn Node Authentication</title>\n  <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">\n  <link rel="stylesheet" type="text/css"\n    href="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.97.5/css/materialize.min.css">\n  <style>\n    .card:hover {\n      box-shadow: 0 10px 20px rgba(0, 0, 0, 0.19), 0 6px 6px rgba(0, 0, 0, 0.23);\n      margin-bottom: 54px;\n    }\n  </style>\n</head>\n\n<body>\n  <nav class="light-blue lighten-1" role="navigation">\n    <div class="nav-wrapper container">\n      <a id="logo-container" href="#" class="brand-logo">Node Authentication</a>\n      <a href="/logout" class="right">Logout</a>\n    </div>\n  </nav>\n  <div class="section no-pad-bot" id="index-banner">\n    <div class="container">\n      <br><br>\n      <div class="row center">\n        <div class="col s12">\n          <div class="card">\n            <div class="card-content blue lighten-3">\n              <span class="card-title white-text"><strong><i class="large material-icons">person</i>\n                </strong></span>\n            </div>\n            <div class="card-action">\n              <h5><b><%= user.displayName %></b></h5>\n              <p><strong>Linkedin id</strong>: <%= user.id %></p>\n            </div>\n          </div>\n        </div>\n      </div>\n    </div>\n  </div>\n</body>\n\n</html>
\n
    \n
  1. Finally, when you are done with the above code you can now write all your app details gathered in step 1 to config.js file created in the root directory
    2. \n
\n
module.exports = {\n  'linkedinAuth': {\n    'clientID': '<CLIENT_ID>', // your App ID\n    'clientSecret': '<CLIENT_SECRET>', // your App Secret\n    'callbackURL': 'http://127.0.0.1:3000/auth/linkedin/callback'\n  }\n}
\n
    \n
  1. Let's have a final check with the repository, aftre follwoing all the steps in the same pordr the directory structure of your code will look like below:
    2. \n
\n
// Final directory structure\nLinkedin-node-authentication/\n  --|node_modules\n  --|views/\n    |--|pages/\n    |----|error.ejs\n    |----|profile.ejs\n    |----|index.ejs\n  --|config.js\n  --|package.json\n  --|package-lock.json\n  --|routes.js\n  --|server.js
\n
    \n
  1. Now run the server by executing below command in the directory Linkedin-node-authentication/
    2. \n
\n
npm start
\n
    \n
  1. Visit the browser with the URL http://localhost:3000
    2. \n
\n

\"Linkedin

\n

Click on the sign in button, and you will be asked to login through Linkedin. Once logged in you will be redirected to profile page as below:

\n

\"Linkedin

\n

The complete sample code for the above tutorial can be found here

\n","frontmatter":{"date":"June 10, 2020","updated_date":null,"description":"Learn social login benefits and how we can implement LinkedIn Login on our website or mobile app.","title":"LinkedIn Login using Node JS and passport","tags":["LinkedIn","Login","NodeJs","PassportJS"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/717d9ce34aacf1736c240b0fa8d67551/58556/linkedin_login_node.webp","srcSet":"/static/717d9ce34aacf1736c240b0fa8d67551/61e93/linkedin_login_node.webp 200w,\n/static/717d9ce34aacf1736c240b0fa8d67551/1f5c5/linkedin_login_node.webp 400w,\n/static/717d9ce34aacf1736c240b0fa8d67551/58556/linkedin_login_node.webp 800w,\n/static/717d9ce34aacf1736c240b0fa8d67551/99238/linkedin_login_node.webp 1200w,\n/static/717d9ce34aacf1736c240b0fa8d67551/135cd/linkedin_login_node.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Aman Agrawal","github":"aman-agrwl","avatar":null}}}},{"node":{"excerpt":"In this blog, we will see how we can read and write into a local file with the help of Deno First, we will create a program which will read…","fields":{"slug":"/engineering/read-and-write-in-a-local-file-with-deno/"},"html":"

In this blog, we will see how we can read and write into a local file with the help of Deno

\n\n

Before You Get Started

\n

This tutorial assumes you have basic knowledge about Deno and you have latest Deno version installed on your system, if you haven't installed Deno on your system or never ran Deno code please look at this great introductory blog - Hello world with Deno

\n

Part 1: Read a file and print text out of it

\n

First, add a file called quotes.txt in the folder you want to run the Deno code, We will read these quotes with the help of Deno

\n
Don't worry about what anybody else is going to do. The best way to predict the future is to invent it. - Alan Kay\nPremature optimization is the root of all evil in programming. - Donald Knuth\nClarity and brevity sometimes are at odds. When they are, I choose clarity.  - Jacob Kaplan-Moss\nOptimism is an occupational hazard of programming; feedback is the treatment. - Kent Beck\nA lot of times, people don't know what they want until you show it to them.  - Steve Jobs\nNine people can't make a baby in a month. - Fred Brooks\nA clever person solves a problem. A wise person avoids it. - Albert Einstein
\n

And then create an index.ts file in which we will write Deno code, we can also write Deno code in javascript instead of Typescript, but as Deno is built on TypeScript we are using Typescript here

\n
const getQuotes = async (fileName: string): Promise<Array<string>> => {\n const decoder = new TextDecoder("utf-8");\n\n const text: string = decoder.decode(await Deno.readFile(fileName));\n return text.split("\\n");\n};\n\nconst quotesArr: Array<string> = await getQuotes("quotes.txt");\n\nconst randomQuote: string =  quotesArr[Math.floor(Math.random() * quotesArr.length)];\nconsole.log(randomQuote);
\n

In the getQuotes function, we are using Deno.readFile #readfile to read the contents of a file as an array of bytes and using TextDecoder to convert the bytes to string and then splitting it in a string array and return

\n

Then we are just picking a randomQuote with Math.random and console.log that on our screen

\n

To run the above code we need to put --allow-read flag in our command as shown below because we need to access the local filesystem to read the file.

\n
deno run --allow-read index.ts
\n

Deno is secure by default, with no file, network, or environment access unless explicitly enabled. You can run deno run --help to see all the available flags for different permissions

\n

Once your program run initially you will see that Deno is compiling the index.ts file and printing a random quote from quotes.txt, if you run the programme again without changing the code it will not compile it again and will just show another random quote.

\n
deno run --allow-read index.ts\nCompile file:///C:/Users/PuneetSingh/Documents/deno_fs/index.ts\nPremature optimization is the root of all evil in programming. - Donald Knuth\n\n\ndeno run --allow-read index.ts\nA lot of times, people don't know what they want until you show it to them.  - Steve Jobs
\n

Part 2: Create a file and write text in it

\n

Let's create another TypeScript file write.ts and put the below code in it

\n
import { readLines } from "https://deno.land/std@v0.52.0/io/bufio.ts";\n\nconsole.log('Start typing...');\n\nconst encoder = new TextEncoder();\nawait Deno.writeFile("input.txt", new Uint8Array());\n\n// Listen to stdin input by readLines\nfor await(const line of readLines(Deno.stdin)) {\n   const data = encoder.encode(line+"\\n");\n   await Deno.writeFile("input.txt", data, {append: true});\n   console.log("Wrote the above text in input.txt\\n") \n}
\n

In the above code we are using readLines to raed user input line by line, Every time we run the code Deno.writeFile(\"input.txt\", new Uint8Array()) will create an empty input.txt file in the folder.

\n

Then const line of readLines(Deno.stdin) in a loop will wait for the user to input any text, as we will give any input Deno.writeFile with {append: true} is used to append data in input.txt

\n

Let's run the program, Once we run it, whatever text we will give to the program through standard input will be written to input.txt

\n
deno run --allow-write write.ts\n\nStart typing...\nThis is a demo for Deno\nWrote the above text in input.txt\n\nIn this demo, we will write some text in a file\nWrote the above text in input.txt
\n

If you check the input.txt file you will found the content which was given as input

\n
This is a demo for Deno\nIn this demo, we will write some text in a file
\n

Now you know how to read from a text file and how to write in a text file with Deno, You can found the complete source code used in the above blog on our Github Repo

\n","frontmatter":{"date":"June 09, 2020","updated_date":null,"description":null,"title":"Read and Write in a local file with Deno","tags":["Deno"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.6666666666666667,"src":"/static/d11d2715523eeb315fdcc7727f48ec20/ad85c/deno_file_system.webp","srcSet":"/static/d11d2715523eeb315fdcc7727f48ec20/61e93/deno_file_system.webp 200w,\n/static/d11d2715523eeb315fdcc7727f48ec20/1f5c5/deno_file_system.webp 400w,\n/static/d11d2715523eeb315fdcc7727f48ec20/ad85c/deno_file_system.webp 600w","sizes":"(max-width: 600px) 100vw, 600px"}}},"author":{"id":"Puneet Singh","github":"puneetsingh24","avatar":null}}}},{"node":{"excerpt":"What is Deno? Deno is a JavaScript/TypeScript runtime with secure defaults and great developer experience. It's built on V8, Rust, and Tokio…","fields":{"slug":"/engineering/build-a-cli-tool-using-deno/"},"html":"

What is Deno?

\n

Deno is a JavaScript/TypeScript runtime with secure defaults and great developer experience. It's built on V8, Rust, and Tokio.\nI suggest you watch these talks by Ryan: He talks about his mistakes with Nodejs here and a more in-depth look into deno here

\n
Features
\n\n

Let's Build Something!!!

\n

In this article, we're going to build a simple cli tool to demonstrate some of the features of deno. Our cli will be interacting with a COVID API to fetch live data.

\n
\n

Requirement: make sure you have deno installed. If you don't, refer to this link. It's pretty straightforward.

\n
\n

Deno has the entry file mod.ts so we will follow the same in this article if you are following this article along with the coding you can create a folder named covid-cli, inside that folder you can create a file called mod.ts and copy the below code there.

\n
const { args } = Deno;\nimport { parse } from "https://deno.land/std/flags/mod.ts";\n\nconsole.dir(parse(args));
\n

Here the parse(args, options = {}); contains two parameters where args is an Array and options is an object, let try to run the above code using this cmd.

\n
deno run mod.ts arg1 -f hello --flag World --booleanFlag
\n

After running the above code you will see the output as

\n
{ _: [ "arg1" ], f: "hello", flag: "World", booleanFlag: true }
\n
\n

The first property in the object is always an array containing all arguments that did not have an option associated with them(i.e it doesn't match -f or --flag). If you do not pass a corresponding value to a flag, it defaults to true.

\n
\n

I will be using the this postman doc for all the COVID related API and we will perform the below to action through our CLI.

\n
    \n
  1. A summary of new and total cases globally updated daily.
    2. \n
  2. A summary of new and total cases per country updated daily.
    3. \n
\n

Let's write out the function for our first command, so our mod.ts file will look like this.

\n
const { args } = Deno;\nimport { parse } from "https://deno.land/std/flags/mod.ts";\n\n// flags:\n// -h, --help: display help message\n// -g, --global: display global stats\n// -c, --country: get data of mentioned country\n\nconst BASE_URL: string = "https://api.covid19api.com/"\nconst parsedArgs = parse(args)\n\nasync function getGlobalStats() {\n    const res = await fetch(`${BASE_URL}summary`)\n    const data = await res.json();\n    console.log(data["Global"])\n}
\n

Here, we have an async function that returns the data from our API call. We're making a fetch request (yes, deno has browser functionality in-built) to the API endpoint to get the global stat of covid19.

\n

The function for the second command looks very similar, just we need to filter our data only for a particular country which is provided.

\n
async function getCountryStats(country: string) {\n  if (country) {\n    const res = await fetch(`${BASE_URL}summary`);\n    const data = await res.json();\n    const index = data["Countries"].findIndex((c: any) => c.Country.toLowerCase() === country.toLowerCase())\n    if (index !== -1) {\n        console.log(data["Countries"][index])\n    } else {\n        console.log("Country Not Found")\n    }\n  } else {\n    console.log("Country Name is needed")\n  }\n}
\n

We will now write our main() function. We have a switch statement to check the first flag that was passed and calls the appropriate function. The default case simply displays a welcome message. Let add the below code in our mod.ts file

\n
async function main() {\n  switch (Object.keys(parsedArgs)[1]) {\n    case "help":\n    case "h":\n      console.log(displayHelpMsg());\n      break;\n    case "global":\n    case "g":\n      await getGlobalStats();\n      break;\n    case "country":\n    case "c":\n       let country = parsedArgs.c || parsedArgs.country || ""\n       await getCountryStats(country)\n       break;\n    default:\n       console.log(displayHelpMsg());\n  }\n}\n\nmain()
\n

And our displayHelpMsg() will look something like this

\n
function displayHelpMsg() {\n  return "flags:\\n-h, --help: display help message\\n-g, --global: display global stats\\n-c, --country: get data of mentioned country ";\n}
\n

Testing Time!!!

\n

To test our program, we're going to run $ deno run --allow-net mod.ts -g. We should get the following result:

\n\n

\"global-data\"

\n\n

\"country-data\"

\n\n

\"help\"

\n

That's all there is for our cli tool. If you'd like to see the full code, the repository is linked here. In conclusion, Deno is a very exciting project especially because you get all the benefits of typescript out of the box without the need to compile your files to js.

\n

You can build a lot with it, ranging from cli Programs to HTTP servers. Do have a look at one of my blog where I have built a basic calculator app using the abc module.

\n","frontmatter":{"date":"June 08, 2020","updated_date":null,"description":null,"title":"Build A Simple CLI Tool using Deno","tags":["Deno","CLI","Programming"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/c24ce77aa8d49761ef8a949cc2a9e06c/58556/cli-tool.webp","srcSet":"/static/c24ce77aa8d49761ef8a949cc2a9e06c/61e93/cli-tool.webp 200w,\n/static/c24ce77aa8d49761ef8a949cc2a9e06c/1f5c5/cli-tool.webp 400w,\n/static/c24ce77aa8d49761ef8a949cc2a9e06c/58556/cli-tool.webp 800w,\n/static/c24ce77aa8d49761ef8a949cc2a9e06c/ffc94/cli-tool.webp 860w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Mohammed Modi","github":"mohammed786","avatar":null}}}},{"node":{"excerpt":"Deno, the creation of Ryan Dahl is a simple, modern, and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust. As…","fields":{"slug":"/engineering/create-rest-api-in-deno/"},"html":"

Deno, the creation of Ryan Dahl is a simple, modern, and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust. As Deno 1.0.0 has released, there is much-awaited curiosity amongst developers around working with this new stack.

\n

When it comes to learning a new language, the first thing that comes to our mind is the creation of a todo app, supporting CRUD functionality. So here we will be creating a very simple Todo application using the Deno.

\n

So before starting I assume you have installed Deno on your system, if not then you can find the link here.\nFor the database, we will be using the JSON file as of now to completely focus on creating web API using Deno. Not more words and now let's start.

\n

The file structure we are going to follow is as below

\n
  // Final directory structure\n  deno-todo-api/\n    --|controllers/\n      |--|todo.ts\n      |data/\n      |--|todos.ts\n      |interfaces/\n      |--|Todo.ts\n      |routes/\n      |--|todo.ts\n    --|server.ts\n
\n

At any point in time, if you are stuck somewhere, you can follow this link to get the complete code.

\n
    \n
  1. Create a directory named deno-todo-api and move into that directory
    2. \n
\n
  mkdir deno-todo-api && cd deno-todo-api
\n
    \n
  1. Create the file server.ts in the root of the directory.
    2. \n
  2. Write the following code into the server.ts file to start a server
    3. \n
\n
import { Application, Router } from "https://deno.land/x/oak@v17.1.4/mod.ts";\n\nconst app = new Application();\nconst port: number = 8080;\n\nconst router = new Router();\nrouter.get("/", ({ response }: { response: any }) => {\n  response.body = {\n    message: "Rest API tutorial with Deno",\n  };\n});\napp.use(router.routes());\napp.use(router.allowedMethods());\n\nconsole.log('running on port ', port);\nawait app.listen({ port });
\n

Unlike NodeJS Deno does not need the package.json file for dependency management. Dependency management is simplified by having a list of modules and their respective URLs.

\n

Here we have used oak, a middleware framework for Deno's HTTP server, including a router middleware.

\n
    \n
  1. server.ts is the entry point for our web application. To check it run the following command in the root directory
    2. \n
\n
deno run --allow-net server.ts
\n

Open the browser and hit the URL http://localhost:8080/

\n

You can see the following output in your browser

\n

\"Browser

\n
    \n
  1. Now following the directory structure, we will create following folders in our project with the help of below command
    2. \n
\n
mkdir controllers data interfaces routes
\n
    \n
  1. First of all, we will create dummy data to play with our todo APIs.Go to the data folder and create a file called todos.ts and the following code into it
    2. \n
\n
import { v4 } from "https://deno.land/std/uuid/mod.ts";\n// interface\nimport Todo from '../interfaces/Todo.ts';\n\nlet todos: Todo[] = [\n  {\n    id: v4.generate(),\n    task: 'Hello world app with Deno',\n    done: true,\n  },\n  {\n    id: v4.generate(),\n    task: 'Simple Rest API with Deno',\n    done: false,\n  },\n];\n\nexport default todos;
\n

We will be using v4 provided by the uuid module to generate unique IDs.

\n
    \n
  1. Now create a file in interface/ folder Todo.ts and paste the following code.
    2. \n
\n
export default interface Todo {\n  id: string,\n  task: string,\n  done: boolean,\n}
\n

What are the interfaces??

\n

An interface defines the specifications of an entity.

\n
\n

One of TypeScript’s core principles is that type checking focuses on the shape that values have. In TypeScript, interfaces fill the role of naming these types and are a powerful way of defining contracts within your code as well as contracts with code outside of your project.

\n
\n
    \n
  1. Now create a file named todo.ts in controllers/ directory and paste the following code
    2. \n
\n
import { v4 } from "https://deno.land/std/uuid/mod.ts";\n// interfaces\nimport Todo from "../interfaces/Todo.ts";\n// stubs\nimport todos from "../data/todos.ts";\n\nexport default {\n  getAll: ({ response }: { response: any }) => {\n    response.status = 200;\n    response.body = {\n      data: todos\n    };\n  },\n  create: async (\n    { request, response }: { request: any; response: any },\n  ) => {\n    const body = await request.body();\n    if (!request.hasBody) {\n      response.status = 400;\n      response.body = {\n        message: "Please provide the task detail and  status",\n      };\n      return;\n    }\n    let newTodo: Todo = {\n      id: v4.generate(),\n      task: body.value.todo,\n      done: false,\n    };\n    let data = [...todos, newTodo];\n    response.body = {\n      data\n    };\n  },\n  getById: (\n    { params, response }: { params: { id: string }; response: any },\n  ) => {\n    const todo: Todo | undefined = todos.find((t) => {\n      return t.id === params.id;\n    });\n    if (!todo) {\n      response.status = 404;\n      response.body = {\n        message: "No task found related to given ID",\n      };\n      return;\n    }\n    response.status = 200;\n    response.body = {\n      data: todo\n    };\n  },\n  update: async (\n    { params, request, response }: {\n      params: { id: string },\n      request: any,\n      response: any,\n    },\n  ) => {\n    const todo: Todo | undefined = todos.find((t) => t.id === params.id);\n    if (!todo) {\n      response.status = 404;\n      response.body = {\n        message: "No todo found",\n      };\n      return;\n    }\n\n    const body = await request.body();\n    const updatedData: { task?: string; done?: boolean } = body.value;\n\n    let newTodos = todos.map((t) => {\n      return t.id === params.id ? { ...t, ...updatedData } : t;\n    });\n    response.status = 200;\n    response.body = {\n      data: newTodos,\n    };\n  },\n  delete: (\n    { params, response }: { params: { id: string }; response: any },\n  ) => {\n    const allTodos = todos.filter((t) => t.id !== params.id);\n\n    response.status = 200;\n    response.body = {\n      data: allTodos,\n    };\n  },\n};
\n
    \n
  1. Now go to routes and create todo.ts file in it and paste the following code
    2. \n
\n
import { Router } from "https://deno.land/x/oak/mod.ts";\n\nconst router = new Router();\n// controller\nimport todoController from "../controllers/todo.ts";\n\nrouter\n  .get("/todos", todoController.getAll)\n  .post("/todos", todoController.create)\n  .get("/todos/:id", todoController.getById)\n  .put("/todos/:id", todoController.update)\n  .delete("/todos/:id", todoController.delete);\n\nexport default router;
\n
    \n
  1. Now since we have created the complete MVC project for our todo APIs, we will be going to update our main server.ts file with following code
    2. \n
\n
import { Application, Router } from "https://deno.land/x/oak/mod.ts";\nimport todoRouter from "./routes/todo.ts"; // added the router call\n\nconst app = new Application();\nconst port: number = 8080;\n\napp.use(todoRouter.routes()); // Intitialize the router with our application. \napp.use(todoRouter.allowedMethods());\n\napp.addEventListener("listen", ({ secure, hostname, port }) => {\n  const protocol = secure ? "https://" : "http://";\n  const url = `${protocol}${hostname ?? "localhost"}:${port}`;\n  console.log(`Listening on: ${port}`);\n});\n\nawait app.listen({ port });
\n
    \n
  1. Now run again the server with the following command
    2. \n
\n
deno run --allow-net server.ts
\n

Now open the postman and hit the get URL http://localhost:8080/todos/

\n

\"Browser

\n

To check the getByID router, copy the ID of any task and hit the URL like

\n

http://localhost:8080/todos/:id

\n

You will be getting output like below

\n
{\n    "data": {\n        "id": "eeacacdc-e55b-4299-aab7-5f631a2e3975",\n        "task": "Hello world app with Deno",\n        "done": true\n    }\n}
\n

Similarly, we can verify the complete crud API created. Below is the reference of all APIs created in the blog post

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
APIMethodDescription
http://localhost:8080/todos/GETFetch All todos
http://localhost:8080/todos/{id}GETFetch todo by ID
http://localhost:8080/todos/POSTCreate New todo
http://localhost:8080/todos/{id}PUTUpdate todo by ID
http://localhost:8080/todos/{id}DELETEDelete todo by ID
\n

You can find the complete code of the repo here

\n","frontmatter":{"date":"June 08, 2020","updated_date":null,"description":null,"title":"Create REST API using deno ","tags":["Deno","REST","API"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/4a65a81c1ab5e2211f19e9aeeb888f6b/58556/task.webp","srcSet":"/static/4a65a81c1ab5e2211f19e9aeeb888f6b/61e93/task.webp 200w,\n/static/4a65a81c1ab5e2211f19e9aeeb888f6b/1f5c5/task.webp 400w,\n/static/4a65a81c1ab5e2211f19e9aeeb888f6b/58556/task.webp 800w,\n/static/4a65a81c1ab5e2211f19e9aeeb888f6b/99238/task.webp 1200w,\n/static/4a65a81c1ab5e2211f19e9aeeb888f6b/135cd/task.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Aman Agrawal","github":"aman-agrwl","avatar":null}}}},{"node":{"excerpt":"We're delightfully announcing the open source automation suite to test all the standard authentication cases of LoginRadius Identity…","fields":{"slug":"/engineering/opensource-automation-for-identity-experience-framework/"},"html":"

We're delightfully announcing the open source automation suite to test all the standard authentication cases of LoginRadius Identity Experience Framework.\nThe details have been given below.

\n\n

idx auto tester

\n

About LoginRadius Identity Experience Framework

\n

Identity Experience Framework is a ready-to-use solution for all the necessary actions. It is a set of registration, authentication, and related web pages such as forgot password, profile. It allows you to customize the UI and UX elements as per your requirements.

\n

Why to use this automation suite?

\n

The Standard Authentication Functionality which is available with LoginRadius Identity Experience Framework can be tested via using these automation scripts. By running all the scripts, you can ensure your implementation.

\n

What is the technology/framework used to build this automation suite?

\n\n

Test cases covered:

\n\n

Note: Currently, the test cases are scripted to run with only 'Required Email Verification' flow.

\n

What's next?

\n

We are continuously working on improving this automation suite and soon we will be announcing the roadmap for automation suite.

\n","frontmatter":{"date":"June 04, 2020","updated_date":null,"description":null,"title":"Automation for Identity Experience Framework is now open-source !!!","tags":["OpenSource","Automation"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/51af1e97aec2b39f25f6184d64fe646c/58556/automation_ief.webp","srcSet":"/static/51af1e97aec2b39f25f6184d64fe646c/61e93/automation_ief.webp 200w,\n/static/51af1e97aec2b39f25f6184d64fe646c/1f5c5/automation_ief.webp 400w,\n/static/51af1e97aec2b39f25f6184d64fe646c/58556/automation_ief.webp 800w,\n/static/51af1e97aec2b39f25f6184d64fe646c/99238/automation_ief.webp 1200w,\n/static/51af1e97aec2b39f25f6184d64fe646c/135cd/automation_ief.webp 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Sudhey Sharma","github":"sudheysharma","avatar":null}}}}]},"markdownRemark":{"excerpt":"Introduction Ever wondered how apps like Spotify, Netflix, or Slack manage seamless login experiences across devices? Many of them use JWT…","fields":{"slug":"/engineering/how-to-integrate-jwt/"},"html":"

Introduction

\n

Ever wondered how apps like Spotify, Netflix, or Slack manage seamless login experiences across devices? Many of them use JWT, or JSON Web Tokens, a compact, stateless method for securely transmitting user identity and session data across services.

\n

With JWT token authentication, identity information is embedded in a signed token, allowing you to maintain user sessions without server-side storage. This approach is highly scalable and ideal for modern architectures like SPAs, mobile apps, and microservices.

\n

In this blog, we’ll walk you through what is JWT, why use it, and how to implement JWT authentication using LoginRadius.

\n

You’ll learn what JWT is, why it’s effective, and how it works in real-world applications. We'll cover both integration methods (IDX and Direct API), generating your signing key, managing sessions, storing the JWT token securely, and applying best practices throughout.

\n

Whether you're a developer, product manager, or IAM architect, this guide offers a complete foundation for implementing JWT token authentication into your application stack.

\n

What is JWT?

\n

JSON Web Token (JWT) is an open standard (RFC 7519) used to transmit information securely between parties as a JSON object. It’s compact, self-contained, and digitally signed, making it a reliable format for authentication and authorization across modern applications.

\n

A JWT consists of three parts:

\n
    \n
  1. Header – Contains metadata like the type of token and signing algorithm (e.g., HS256).
    2. \n
  2. Payload – Stores the actual data or “claims,” such as user ID, roles, and token expiry.
    3. \n
  3. Signature – A cryptographic hash that ensures the token hasn’t been tampered with.
    4. \n
\n

Example of a token structure:

\n

<base64Header>.<base64Payload>.<signature>

\n

Why Use JWT?

\n\n

How JWT Works?

\n

\"Flowchart

\n
    \n
  1. A user logs in with credentials.
    2. \n
  2. Your app (or identity provider like LoginRadius) issues a signed JWT.
    3. \n
  3. The client stores the token and sends it with each request (usually in the Authorization header).
    4. \n
  4. The server validates the token’s signature and claims.
    5. \n
  5. If valid, access is granted — without any session stored on the backend.
    6. \n
\n

JWT simplifies identity verification, especially when you're building apps that talk to APIs or need to scale without centralized session storage.

\n

JWT Authentication with LoginRadius: Overview

\n

LoginRadius provides robust support for JWT (JSON Web Token) authentication, which allows for flexible and secure access control across different digital platforms. Whether you're building a fully custom identity flow or using a pre-built interface, the platform supports various integration approaches depending on your architecture.

\n

If you're looking to understand how to implement JWT token authentication effectively, LoginRadius offers two primary implementation models that cater to different levels of customization and control:

\n

1. IDX Implementation – JWT through a Hosted Login Page

\n

The IDX-hosted login approach enables secure, standards-compliant, JWT-based authentication without requiring you to build a custom login interface. This is a strategic option for fast, compliant, and user-friendly deployments.

\n\n

Configuration Steps:

\n
    \n
  1. Enable JWT Login
    2. \n
  2. Go to authentication configuration settings and enable JWT Login in the Admin Console.
    3. \n
\n

\"Screenshot

\n
    \n
  1. Specify your signing algorithm and expiry policy, and define your JWT Secret Key.
    2. \n
  2. Input a secure JWT signing key.
    3. \n
  3. Specify token expiry duration (e.g., 15–60 minutes)
    4. \n
  4. Select the desired algorithm —HS256 for symmetric signing (same key signs and verifies)
    5. \n
  5. RS256 for asymmetric signing, where LoginRadius securely stores the private key used to sign the JWT.
    6. \n
  6. Your app or backend service uses the public key to validate the token signature.
    7. \n
  7. LoginRadius provides a JWKS (JSON Web Key Set) endpoint to dynamically fetch and rotate public keys, ensuring trust without key exposure.
    8. \n
  8. Update IDX Template for Callback
    9. \n
  9. Modify your IDX login page template to retrieve the JWT post-login. You can access the token via redirect URL parameters or secure JavaScript callbacks.
    10. \n
\n

Example Response:

\n

{

\n

\"access_token\": \"eyJhbGciOiJIUzI1NiIsInR...\",

\n

\"expires_in\": 1800

\n

}

\n

This integration approach works best for all teams that want effective identity workflows without the complexity of building proprietary login screens, something that is crucial for customer portals, onboarding of mobile applications, and even managing access for business partners.

\n

2. Direct API Implementation – Self Managed Login

\n

If you’re building a custom login UI or working in a headless environment, LoginRadius lets you generate and handle JWTs directly through its Authentication APIs. Here’s how you can programmatically perform token authentication using the classic method:

\n\n

Configuration Steps:

\n

Step 1: Authenticate via API:

\n\n

Include the user’s credentials (email + password) in the request body.

\n

Step 2: Get JWT in Response

\n\n

{

\n

\"access_token\": \"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...\",

\n

\"expires_in\": 3600

\n

}

\n

Step 3: JWT Decoding and Validation

\n\n

Step 4: Set Custom Claims (Optional)

\n

With LoginRadius, it is possible to customize the payload to include user roles and/or any additional metadata. You can set custom JWT claims on the Admin Console.

\n

With this method, you have complete customization over login flows while using LoginRadius to issue signed JWTs for user session management.

\n

NOTE- With either method, LoginRadius ensures that JWTs are securely signed, optionally short-lived, and compatible with standard token validation libraries, making integration seamless for everyone.

\n

To get started with JWT implementation, you can read our complete developer documentation.

\n

Hosted Login vs Direct API

\n

\"Illustration

\n

What is Session Management and How It Works with JWT

\n

Session management is how your app keeps track of a user after they log in so they don’t have to prove who they are with every request.

\n

In traditional apps, sessions are stored on the server using session IDs. Every time a request comes in, the server checks that session ID to verify the user.

\n

In modern apps, especially SPAs and APIs, JWTs are used to manage sessions without needing server-side storage; this is called stateless session management. The token itself carries the user’s identity, roles, and expiration details. As long as the token is valid, the user stays logged in.

\n

Good session management ensures:

\n\n

How LoginRadius Handles Session Management with JWT:

\n
    \n
  1. \n

    User Logs In

    \n\n
    2. \n
  2. \n

    Client Stores the Token

    \n\n
    3. \n
  3. \n

    Access Token Expiry

    \n\n
    4. \n
  4. \n

    Token Renewal

    \n\n
    5. \n
  5. Logout and Token Revocation Strategy
    6. \n
\n

When the user logs out, both the access token and refresh token should be cleared from client storage.

\n\n

Combining these strategies gives you greater control over token misuse and enables a robust, enterprise-grade logout flow.

\n

\"illustration

\n

How to Store JWT Tokens?

\n

When you implement JWT-based authentication, the client (browser or mobile app) needs a way to store the access token and, optionally, the refresh token after they are issued by the authentication server. This stored token is then attached to every subsequent request to prove the user's identity.

\n

Choosing where to store the JWT is a crucial security decision. The most common storage options are:

\n\n

Each option has trade-offs between security, accessibility, and persistence, and the right choice depends on your application's architecture and threat model.

\n

Recommended Storage Strategy

\n\n

Best Practices for Storing JWTs

\n
    \n
  1. Never store sensitive tokens (like refresh tokens) in localStorage or sessionStorage.
    2. \n
  2. Use Secure and HttpOnly flags with cookies to prevent JavaScript access and ensure transmission only over HTTPS.
    3. \n
  3. Set the SameSite=Strict or Lax attribute on cookies to protect against CSRF.
    4. \n
  4. Use short-lived access tokens and rotate refresh tokens regularly.
    5. \n
  5. Implement CSP (Content Security Policy) to reduce XSS risk.
    6. \n
  6. Avoid storing any tokens in frontend code (e.g., hardcoded in JS files).
    7. \n
\n

Conclusion

\n

JWT authentication with LoginRadius offers a modern, stateless approach to managing sessions across distributed systems. The IDX integration is ideal for rapid deployment, while the Direct API model is best for organizations needing deep customization and integration flexibility.

\n

With robust token signing, refresh capabilities, and centralized control, LoginRadius provides a future-ready foundation for secure, scalable identity architecture. Contact us to know more about JWT authentication and implementation guide.

\n

FAQs

\n

1. What is JWT authentication used for?

\n

A: JWT authentication securely verifies user identities, enabling stateless session management across web, mobile apps, and microservices without server-side session storage.

\n

2. How does LoginRadius simplify JWT integration?

\n

A: LoginRadius simplifies JWT integration by offering hosted IDX login pages and direct API-based authentication methods, enabling rapid deployment and deep customization.

\n

3. Is JWT authentication secure?

\n

A: Yes, JWT authentication is secure when implemented with best practices like short-lived tokens, secure storage methods, signature validation, and refresh token rotation.

\n

4. Can JWT tokens be revoked with LoginRadius?

\n

A: Yes, LoginRadius allows revocation of JWT refresh tokens explicitly, and supports strategies like short-lived tokens and key rotation to manage token lifecycles securely.

\n","frontmatter":{"date":"April 15, 2025","updated_date":null,"description":"Discover JWT (JSON Web Token) authentication, its advantages, and how to integrate it seamlessly using LoginRadius' hosted IDX and Direct API methods for secure, scalable identity management.","title":"JWT Authentication with LoginRadius: Quick Integration Guide","tags":["JWT","JSON Web Token","Authentication","Authorization"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":0.7782101167315175,"src":"/static/4cedb7829f98208cbc6d5a9aea4e983d/58556/how-to-integrate-jwt.webp","srcSet":"/static/4cedb7829f98208cbc6d5a9aea4e983d/61e93/how-to-integrate-jwt.webp 200w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/1f5c5/how-to-integrate-jwt.webp 400w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/58556/how-to-integrate-jwt.webp 800w,\n/static/4cedb7829f98208cbc6d5a9aea4e983d/1cc9f/how-to-integrate-jwt.webp 896w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Kundan Singh","github":null,"avatar":null}}}},"pageContext":{"limit":6,"skip":210,"currentPage":36,"type":"//engineering//","numPages":53,"pinned":"5c425581-f474-5ae9-abe7-cf5342db2aaa"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}