As a developer, you should be familiar with StackExchange. There are tons of resources available on there about software development and programming. Out of everything, I have compiled a list of the top 8 resources that I find helpful. These resources cover a wide range of topics such as web development, general programming, and best practices to follow during development.
\n1. Technical things to remember when doing the live (production) deployment of the web application
\nIn this resource, you’ll get a checklist of the things that will make your web application deployment go smoothly as well as how to get good feedback from your users/search engines. It covers many topics such as user interface, user experience, security, SEO, browser compatibility, design, etc.
\nURL : HDPA
\n2. Why can’t software industry deliver faultless projects quickly?
\nHave you ever compared the software industry with other industries such as retail, telecommunications, etc.? The article above covers many of the differences and gives tips around how, as a developer, you can focus on the issues related to software.
\nURL : HDPE
\n3. How can I review my own code?
\nHave you ever reviewed your code? It’s always a fun thing to do… Coding standards and code quality are equally important factors that feed into software quality. In this thread, you’ll find best practices for self-code review that will help improve the quality of the overall software or web application.
\nURL : HDPF
\n4. Must read books for programmers
\nBooks are useful for everyone, regardless of your profession. They impart plenty of information into your brain, which you then process and output as a skill. In this thread, you’ll find a list of helpful books to read as a developer. You can choose what to read based on the technology and system you are familiar with, but my personal favourite is “code complete.”
\nURL : HDPJ
\n5. How to improve programming skills?
\nWe, programmers, are always looking to improve our coding skills, but sometimes only writing code is not enough. This thread has some tips and tricks for how you can improve.
\nURL : HDPL
\n6. Should I become a polyglot programmer?
\nThis thread will help you understand the benefits of learning additional programming languages as a way to improve your thought processes. Understanding more language designs makes you a sharper developer.
\nURL : HDSM
\n7. Selection between “Do it right” and “Do it ASAP”
\nHave you ever been in a tricky situation where you are caught choosing between whether to make the software the right way or to finish it quickly for an upcoming deadline? Well, you are not alone! All developers face the same problem. Go through this thread to understand and choose the right approach for you.
\nURL : HDSX
\n8. For fun: list of programmers cartoons
\nDevelopers enjoy writing software and feel a deep sense of satisfaction when the program they've been working on is executed nicely and goes to production. That is the essential part of our life, but sometimes we can afford to take a break from all the coding and enjoy some nerdy cartoons… Here are some that I like.
\nURL : HDPR
\nI’m sure there are lots of other resources available, so please post your recommendations in the comments section.
\n","frontmatter":{"date":"April 25, 2020","updated_date":null,"description":null,"title":"StackExchange - The 8 best resources every developer must follow","tags":["Programmer","Skills"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/554ba40ae16d5bf67b4e87c50415b366/ee604/8-stackexchange-resources-dev-follow.png","srcSet":"/static/554ba40ae16d5bf67b4e87c50415b366/69585/8-stackexchange-resources-dev-follow.png 200w,\n/static/554ba40ae16d5bf67b4e87c50415b366/497c6/8-stackexchange-resources-dev-follow.png 400w,\n/static/554ba40ae16d5bf67b4e87c50415b366/ee604/8-stackexchange-resources-dev-follow.png 800w,\n/static/554ba40ae16d5bf67b4e87c50415b366/db955/8-stackexchange-resources-dev-follow.png 900w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Kundan Singh","github":null,"avatar":null}}}},{"node":{"excerpt":"In this blog, we’ll be implementing OAuth by Github in a Node.js Application Before You Get Started This tutorial assumes you have: Basic…","fields":{"slug":"/engineering/oauth-implemenation-using-node/"},"html":"In this blog, we’ll be implementing OAuth by Github in a Node.js Application
\nThis tutorial assumes you have:
\nTo implement Github Auth we need to register a new application in Github OAuth Apps.
\nOnce you start the process you will get a form like this.
\nFirst in an empty folder run the below command It essentially just creates the package.json file with all the basic information you will provide. after that, we will install all the dependencies needed in our project Create a file index.js in the root folder of your app and add the following code: Our web server has been set up, now we will add the code related to sending the OAuth request to GitHub using Axios package, at the bottom of the index.js file: Note: The callback URL should be the same as used in the GitHub app configuration. Create an ejs file under path views/pages/index.js, it will render into a nice looking Github authorization page: After it we will create an ejs file under path views/pages/success.js, it will be used to show the user's GitHub information we will get after authorized by Github Note: Here we are also using bootstrap and font-awesome css to make our web pages look good. We have finished building our OAuth authorization page, let's run the application by below command Once our server is running, we can see our social login page on We need to click on the Github Login button, which will redirect us to google login page. You can implement the OAuth in Node.js by the above process, You can found the complete code used in this tutorial on out In this blog, we’ll be implementing authentication with JWT in a NodeJS web application. For this, we’ll be using jsonwebtoken package JWT(JSON Web Token) is a token format. It is digitally-signed, self-contained, and compact. It provides a convenient mechanism for transferring data. JWT is not inherently secure, but the use of JWT can ensure the authenticity of the message so long as the signature is verified and the integrity of the payload can be guaranteed. JWT is often used for stateless authentication in simple use cases involving non-complex systems. Here's an example of JWT: Now, let's authenticate/protect some routes. Pre-requisites: you can install all required packages by using following command: Step 1. First, create a directory structure as below : In the api/models folder, create a file called user userModel.js by running touch api/models/userModel.js. In this file, create a mongoose schema with the following properties: Add the following code In the api/controllers folder, create a file called user userController.js by running touch api/controllers/userController.js In the userController file, create three different handlers to handle by using the following code Note: A hash password was saved in the database using bcrypt. Step 6. In the api/route folder, create a file called user userRoute.js and add the following code: Step 9. Now you just need to run the project by using the following command and try logging by using the JWT. Step 10. Open Postman and create a post request to localhost:3000/auth/register as below: Under the value, add JWT and the token with a space between, like so: Step 11. Then, enter the parameters for the key and value for fetching the profile. You want to create as shown below and send: As we have seen it is fairly easy to build a JWT authentication system with NodeJS, You can found the complete code used in this tutorial here. Note : You can decode or verify your JWT token details with this tool This blog is a short guide on implementing AWS Lambda and SQS together. First we’ll introduce these technologies and explain why they work well together, then walkthrough some configurations and invocation using a simple Nodejs script. What are they?\nAWS Lambda is a popular choice in serverless computing. As an event-driven platform, AWS Lambda requires users to configure event sources in order to run a function. Their built-in support for many AWS services like S3 and SQS as event sources allow for relatively simple configuration. Note that Lambda functions can also be triggered via HTTP(S) by using AWS API Gateway service. AWS SQS (Simple Queue Service) is a queue service with 2 types: standard and FIFO. The major difference is that standard queues guarantee “at-least once” delivery of its messages, while FIFO queues guarantee “exactly-once” delivery. FIFO queues, however, provide lower maximum throughput than standard. As previously mentioned, AWS SQS can be an event source for AWS Lambda. This means that when a message is added to the queue, the configured Lambda function will be invoked with an event containing this message. But why use them together? One limitation for many use cases was the “at-least once” delivery model of events with standard queues. Essentially, there was no guarantee that an event will only be delivered once to a consuming Lambda function. In cases where each event can strictly only be processed once, one would have to employ various strategies resulting in higher overhead and complexity. But, this is no longer an issue because recently the AWS team added support for FIFO queues as event sources to Lambda functions. Walkthrough 1. Starting with SQS, add a standard queue. 2. Now, add a Lambda function: 3. Create a new execution role with the following configs: 5. Add a trigger: 6. Programmatically enqueue a message into SQS with the following code in Nodejs: a. Create package.json with `npm init` In this blog, we’ll be implementing OAuth in node js application via Google. For this, we’ll be using Passport.js, an authentication package for Node.js. Here’s a quick guide on implementing OAuth 2.0 in node js. This tutorial assumes you have: We can create a client ID and client secret using its Google API Console. You need to follow below steps once you open Google Auth API Console Note: If Google doesn't support To create OAuth nodejs authentication, first in an empty folder run the below command It essentially just creates the package.json file with all the basic information you will provide. after that, we will install all the dependencies needed in our project Create a file index.js in the root folder of your app and add the following code: Our web server has been set up, now we will add the code related to the passport at the bottom of the index.js file: Now, at last, we are ready to implement Google Authentication in our app, Add the following code at the bottom of your index.js file, use your client Id and Secret instead of placeholders: Note: The callback URL should be the same as used in the google app configuration. Create an ejs file under path views/pages/auth.js, it will render into a nice looking social login page: After it we wll create an ejs file under path views/pages/success.js, it will be used to show the user profile information we will get after authenticated by google Note: Here we are also using bootstrap and font-awesome css to make our web pages look good. We have finished building our social login page, let's run the application by below command Once our server is running, we can see our social login page on 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. We’ll implement the most relevant and widely useful solutions to facilitate a smooth transition for our customers. Please subscribe to our blog for more information. We’ll update you on how we help with the third-party cookie phase-out. The proposed changes to phase out third-party cookies and suggested alternatives are evolving as Google has been actively collaborating and discussing changes with the border community. Moreover, browsers like Firefox, Safari, and Edge may approach restricting third-party cookies differently than Google does. From LoginRadius, we’ll keep you updated on what we’re doing as a leading Customer Identity and Access Management (CIAM) vendor to prepare for the third-party cookie phase-out. Top-level site: It is the primary site a user has visited. First-party cookie: A cookie set by the top-level site. Third-party cookie: A cookie set by a domain other than the top-level site. For example, let’s assume that a user has visited Step 2: Initialize a node.js project with all the dependencies
\n
\nnpm init\n
\n
\nnpm install express ejs axios --saveStep 3: Writing express server code to accept web requests
\n
\n// index.js\n\n/* EXPRESS */\nconst express = require('express');\nconst app = express();\n\napp.set('view engine', 'ejs');\nvar access_token = "";\n\napp.get('/', function(req, res) {\n res.render('pages/index',{client_id: clientID});\n});\n\nconst port = process.env.PORT || 2400;\napp.listen(port , () => console.log('App listening on port ' + port));
\n// index.js\n\n// Import the axios library, to make HTTP requests\nconst axios = require('axios')\n// This is the client ID and client secret that you obtained\n// while registering on github app\nconst clientID = 'xxxxxxxxxxxx'\nconst clientSecret = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxx'\n\n// Declare the callback route\napp.get('/github/callback', (req, res) => {\n\n // The req.query object has the query params that were sent to this route.\n const requestToken = req.query.code\n \n axios({\n method: 'post',\n url: `https://github.com/login/oauth/access_token?client_id=${clientID}&client_secret=${clientSecret}&code=${requestToken}`,\n // Set the content type header, so that we get the response in JSON\n headers: {\n accept: 'application/json'\n }\n }).then((response) => {\n access_token = response.data.access_token\n res.redirect('/success');\n })\n})\n\napp.get('/success', function(req, res) {\n\n axios({\n method: 'get',\n url: `https://api.github.com/user`,\n headers: {\n Authorization: 'token ' + access_token\n }\n }).then((response) => {\n res.render('pages/success',{ userData: response.data });\n })\n});Step 4: Creating a Login and Profile page
\n
\n<!-- views/index.ejs -->\n<!doctype html>\n<html>\n<head>\n <title>Github OAuth</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-primary">\n <h1><span class="fa fa-github"></span> Github OAuth</h1>\n <p>Authorize your app with:</p>\n <a href="https://github.com/login/oauth/authorize?client_id=<%= client_id %>" class="btn btn-danger"><span class="fa fa-github"></span> Github Login</a>\n </div>\n</div>\n</body>\n</html>
\n<!-- views/success.ejs -->\n<!doctype html>\n<html>\n <head>\n <title>Github OAuth</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-primary text-center"><span class="fa fa-github"></span> Github Information</h1>\n <div class="row">\n <div class="col-sm-6">\n <div class="well">\n <p>\n <strong>Name</strong>: <%= userData.name %><br>\n <strong>Username</strong>: <%= userData.login %><br>\n <strong>Company</strong>: <%= userData.company %><br>\n <strong>Bio</strong>: <%= userData.bio %>\n </p>\n </div>\n </div>\n </div>\n </div>\n </div>\n </body>\n</html>
\nnode index.jshttp://localhost:2400/What is JWT?
\n
\neyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6Im9sYXR1bmRlZ2FydWJhQGdtYWlsLmNvbSIsIm\n
\n
\nnpm install express mongoose bcrypt --saveJWTApp
\n-api\n--models\n----userModel.js\n--controllers\n----userController.js\n--route\n----userRoute.js\n--server.jsStep 2. Install “jsonwebtoken” packageby using following command
\n
\n npm install jsonwebtoken -- saveStep 3. Create the user model
\n\n
\n
\n'use strict';\n\nvar mongoose = require('mongoose'),\n bcrypt = require('bcrypt'),\n Schema = mongoose.Schema;\n\n/**\n * User Schema\n */\nvar UserSchema = new Schema({\n fullName: {\n type: String,\n trim: true,\n required: true\n },\n email: {\n type: String,\n unique: true,\n lowercase: true,\n trim: true,\n required: true\n },\n hash_password: {\n type: String\n },\n created: {\n type: Date,\n default: Date.now\n }\n});\n\nUserSchema.methods.comparePassword = function(password) {\n return bcrypt.compareSync(password, this.hash_password);\n};\n\nmongoose.model('User', UserSchema);Step 4. Create the user handlers
\n
\n'use strict';\n\nvar mongoose = require('mongoose'),\n jwt = require('jsonwebtoken'),\n bcrypt = require('bcrypt'),\n User = mongoose.model('User');\n\nexports.register = function(req, res) {\n var newUser = new User(req.body);\n newUser.hash_password = bcrypt.hashSync(req.body.password, 10);\n newUser.save(function(err, user) {\n if (err) {\n return res.status(400).send({\n message: err\n });\n } else {\n user.hash_password = undefined;\n return res.json(user);\n }\n });\n};\n\nexports.sign_in = function(req, res) {\n User.findOne({\n email: req.body.email\n }, function(err, user) {\n if (err) throw err;\n if (!user || !user.comparePassword(req.body.password)) {\n return res.status(401).json({ message: 'Authentication failed. Invalid user or password.' });\n }\n return res.json({ token: jwt.sign({ email: user.email, fullName: user.fullName, _id: user._id }, 'RESTFULAPIs') });\n });\n};\n\nexports.loginRequired = function(req, res, next) {\n if (req.user) {\n next();\n } else {\n\n return res.status(401).json({ message: 'Unauthorized user!!' });\n }\n};\nexports.profile = function(req, res, next) {\n if (req.user) {\n res.send(req.user);\n next();\n } \n else {\n return res.status(401).json({ message: 'Invalid token' });\n }\n};
\n'use strict';\nmodule.exports = function(app) {\n var userHandlers = require('../controllers/userController.js');\n // todoList Routes\n app.route('/tasks')\n .post(userHandlers.loginRequired, userHandlers.profile);\n app.route('/auth/register')\n .post(userHandlers.register);\n app.route('/auth/sign_in')\n .post(userHandlers.sign_in);\n};Step 7. Add the following code in server.js
\n
\n'use strict';\n\nvar express = require('express'),\n app = express(),\n port = process.env.PORT || 3000,\n\n\n User = require('./api/models/userModel'),\n bodyParser = require('body-parser'),\n jsonwebtoken = require("jsonwebtoken");\n\nconst mongoose = require('mongoose');\nconst option = {\n socketTimeoutMS: 30000,\n keepAlive: true,\n reconnectTries: 30000\n};\n\nconst mongoURI = process.env.MONGODB_URI;\nmongoose.connect('mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb', option).then(function(){\n //connected successfully\n}, function(err) {\n //err handle\n});\n\napp.use(bodyParser.urlencoded({ extended: true }));\napp.use(bodyParser.json());\n\napp.use(function(req, res, next) {\n if (req.headers && req.headers.authorization && req.headers.authorization.split(' ')[0] === 'JWT') {\n jsonwebtoken.verify(req.headers.authorization.split(' ')[1], 'RESTFULAPIs', function(err, decode) {\n if (err) req.user = undefined;\n req.user = decode;\n next();\n });\n } else {\n req.user = undefined;\n next();\n }\n});\nvar routes = require('./api/routes/userRoutes');\nroutes(app);\n\napp.use(function(req, res) {\n res.status(404).send({ url: req.originalUrl + ' not found' })\n});\n\napp.listen(port);\n\nconsole.log(' RESTful API server started on: ' + port);\n\nmodule.exports = app;
\nnpm start
\nJWT eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6Im9sYXR1bmRlZ2FydWJhQGdtYWlsLmNvbSIsImZ1bGxOYW1lIjoiT2xhdHVuZGUgR2FydWJhIiwiX2lkIjoiNThmMjYzNDdiMTY1YzUxODM1NDMxYTNkIiwiaWF0IjoxNDkyMjgwMTk4fQ.VcMpybz08cB5PsrMSr25En4_EwCGWZVFgciO4M-3ENE
\nCommon reasons include better handling Lambda function invocations and errors. For function invocations, the default concurrency limit is 1000. If a function has reached this limit, any additional invocations will fail with a throttling error. However, with SQS as an event source, events resulting in throttling errors are automatically retried based on set configs. This prevents the loss of events due to unexpected jumps in usage. Additionally, dead-letter queues (DLQ) can be configured as a place where failed events go, to avoid retrying indefinitely. Failed events in DLQ can then be sent somewhere like a DB for analysis.
\nLet’s set up a basic “Hello World” application with SQS and Lambda.
\na. Trusted Entity: Lambda
\nb. Permissions: AWSLambdaBasicExecutionRole; AWSLambdaSQSQueueExecutionRole
\na. Batch size set to 1, so the Lambda Function will process 1 message at a time.
\nconst AWS = require("aws-sdk");\nAWS.config.update({\n region: <AWS_SQS_REGION>, // TODO\n accessKeyId: <AWS_ACCESS_KEY_ID>, // TODO\n secretAccessKey: <AWS_SECRET_ACCESS_KEY> // TODO\n});\n\nconst sqs = new AWS.SQS({ apiVersion: "2012-11-05" });\nsqs.sendMessage({\n MessageBody: JSON.stringify({hello: "world"}),\n QueueUrl: <AWS_SQS_URL> // TODO\n}, (err, data) => (err) ? console.log("Error", err) : console.log("Success", data.MessageId));
\nb. Install aws sdk dependency with `npm i aws-sdk --save`
\nc. Fill in your specific AWS account details. Find AWS_SQS_URL by selecting the queue you created, while AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY require creating a new IAM user with programmatic access. This user also needs permission to push messages into SQS.
\nd. Run script with `node app.js`
\ne. Navigate to Monitoring tab in your Lambda function, the invocations graph should have a new data point (may take a few minutes to update).Before You Get Started
\n\n
\nStep 1: Create a Google client ID and client secret
\n\n
\nhttp://localhost:3000/auth/google/callbackhttp://localhost:3000, then use http://127.0.0.1:3000Step 2: Initialize a node.js project with all the dependencies
\n
\nnpm init\n
\n
\nnpm install express ejs express-session passport passport-google-oauth --saveStep 3: Writing express server code to accept web requests
\n
\n// index.js\n\n/* EXPRESS */\n\nconst express = require('express');\nconst app = express();\nconst session = require('express-session');\n\napp.set('view engine', 'ejs');\n\napp.use(session({\n resave: false,\n saveUninitialized: true,\n secret: 'SECRET' \n}));\n\napp.get('/', function(req, res) {\n res.render('pages/auth');\n});\n\nconst port = process.env.PORT || 3000;\napp.listen(port , () => console.log('App listening on port ' + port));
\n// index.js\n\n/* PASSPORT SETUP */\n\nconst passport = require('passport');\nvar userProfile;\n\napp.use(passport.initialize());\napp.use(passport.session());\n\napp.set('view engine', 'ejs');\n\napp.get('/success', (req, res) => res.send(userProfile));\napp.get('/error', (req, res) => res.send("error logging in"));\n\npassport.serializeUser(function(user, cb) {\n cb(null, user);\n});\n\npassport.deserializeUser(function(obj, cb) {\n cb(null, obj);\n});
\n// index.js\n\n/* Google AUTH */\n \nconst GoogleStrategy = require('passport-google-oauth').OAuth2Strategy;\nconst GOOGLE_CLIENT_ID = 'our-google-client-id';\nconst GOOGLE_CLIENT_SECRET = 'our-google-client-secret';\npassport.use(new GoogleStrategy({\n clientID: GOOGLE_CLIENT_ID,\n clientSecret: GOOGLE_CLIENT_SECRET,\n callbackURL: "http://localhost:3000/auth/google/callback"\n },\n function(accessToken, refreshToken, profile, done) {\n userProfile=profile;\n return done(null, userProfile);\n }\n));\n \napp.get('/auth/google', \n passport.authenticate('google', { scope : ['profile', 'email'] }));\n \napp.get('/auth/google/callback', \n passport.authenticate('google', { failureRedirect: '/error' }),\n function(req, res) {\n // Successful authentication, redirect success.\n res.redirect('/success');\n });Step 4: Creating a Login and Profile page
\n
\n<!-- views/pages/auth.ejs -->\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">\n <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">\n <style>\n body { padding-top:70px; }\n </style>\n</head>\n<body>\n<div class="container">\n <div class="jumbotron text-center text-primary">\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<!-- views/success.ejs -->\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 bootstrap 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-primary 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>: <%= user.id %><br>\n <strong>Email</strong>: <%= user.emails[0].value %><br>\n <strong>Name</strong>: <%= user.displayName %>\n </p>\n </div>\n </div>\n </div>\n </div>\n </div>\n </body>\n</html>
\nnode index.jshttp://localhost:3000/In Conclusion
\nGlossary
\na.com, which might use an embed from loginradius.com to facilitate authentication. If loginradius.com sets a cookie when the user visits a.com, it is called a third-party cookie as the user hasn’t directly visited loginradius.com.References
\n\n","frontmatter":{"date":"July 08, 2024","updated_date":null,"description":"Google Chrome has planned to phase out third-party cookies, which will affect different website functionalities depending on third-party cookies. This blog focuses on how this phase-out affects identity and user authentication and discusses alternatives for overcoming challenges.","title":"How Chrome’s Third-Party Cookie Restrictions Affect User Authentication?","tags":["Identity","Cookies","Chrome"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png","srcSet":"/static/eb7396060c0adc430dbed2d04b63d431/69585/third-party-cookies-phaseout-chrome.png 200w,\n/static/eb7396060c0adc430dbed2d04b63d431/497c6/third-party-cookies-phaseout-chrome.png 400w,\n/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png 800w,\n/static/eb7396060c0adc430dbed2d04b63d431/f3583/third-party-cookies-phaseout-chrome.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Raghunath Reddy","github":"raghunath-r-a","avatar":null}}}},"pageContext":{"limit":6,"skip":216,"currentPage":37,"type":"//engineering//","numPages":52,"pinned":"17fa0d7b-34c8-51c4-b047-df5e2bbaeedb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}