****PROJECT PHASE 2 PART-D *****

AUTHENTICATION:

PROCESS OF VERIFYING WHO SOMEONE IS.

VERIFYING IDENTITY.

USED TO SIGN UP/LOGIN

AUTHORIZATION:

PROCESS OF VERIFYING WHAT SPECIFIC APPLICATIONS,FILES, AND DATA A USER HAS ACCESS TO.

STORING PASSWORDS:

PASSWORDS ARE NEVER STORED IN THE DATABASE DIRECTLY .

THEY ARE STORED IN THEIR HASHED FORM.

A HASH FUNCTION CONVERTS A STRING (READABLE) TO UNRECOGNIZABLE STRING(UNREADABLE) .

THE PASSWORD ENTERED BY THE USER IS SENT TO A HASH FUNCTION AND AN UNREADABLE STRING IS GENERATED .THIS STRING IS STORED IN THE DATABASE.

IT IS VERIFIED FOR AUTHENTICATION.

WHEN AN USER SETS A PASSWORD : abc123 THIS IS CONVERTED INTO AN UNRECOGNIZABLE STRING: str1  BY THE HASH FUNCTION, AND THAT STRING IS STORED IN THE DATABASE.

IF THE USER , WHILE LOGGING IN ENTERS ANOTHER PASSWORD: abc , THIS STRING IS SENT TO THE HASH FUNCTION , IT GENERATES A STRING: str2 (AS THE PASSWORD IS DIFFERENT) . AS str2 DOESNOT MATCH WITH str1(STORED IN DB) LOGIN FAILS.

Comments

Post a Comment

Popular posts from this blog

DATABASE RELATIONSHIPS

Image
 RELATIONSHIPS INCLUDE  ONE - TO -ONE (1x 1)   ONE ENTITY OF A TABLE IS IN RELATION WITH ONLY ONE ENTITY OF ANOTHER. ONE - TO -MANY (1x N)   ONE ENTITY IS IN RELATION WITH MANY MANY - TO - MANY(NxN)   MANY ENTITIES ARE IN RELATION WITH MANY OTHER. ONE- TO-MANY IS MORE HARDER TO BE REPRESENTED THAN ONE - TO - ONE AND MANY - TO - MANY ONE- TO -MANY IT IS CATEGORIZED INTO 3 BASED ON MANY MANY CAN BE IN 3 TYPES 1. ONE -TO-FEW:  SMALL NUMBER (2,5 ,100,500) STORE THE CHILD DOCUMENT INSIDE PARENT TAKE ZOMATO OR AMAZON FOR EXAMPLE, A SINGLE USER CAN HAVE MULTIPLE ADDRESSES. HERE WE DONOT CREATE TWO MODELS FOR USER AND ADDRESS, AS ADDRESS IS ASSOCIATED WITH USER DIRECTILY, WE STORE THE CHILD DOCUMENT INSIDE PARENT. const mongoose = require ( "mongoose" ); const { Schema } = mongoose ; main ()   . then (() => {     console . log ( "connection successful" );   })   . catch (( err ) => {     console . log ( err );...
Read more

ROUTING (GET /) home route

Image
  app . get ( "/" , ( req , res ) => {   let q = 'SELECT COUNT(*) FROM user' ;   try {   connection . query ( q , ( err , result ) => {     if ( err ) throw err ;     let count = result [ 0 ][ 'COUNT(*)' ];     console . log ( count );     res . render ( "home.ejs" ,{ count });   }); } catch ( err ) {   console . log ( err );   res . send ( "error occured" ); } }); app . listen ( port , () => {   console . log ( `listening to port ${ port } ` ); }); HOME.EJS <! DOCTYPE html > < html lang = "en" > < head >     < meta charset = "UTF-8" >     < meta name = "viewport" content = "width=device-width, initial-scale=1.0" >     < title > home </ title > </ head > < body >     < h2 > Total count of users: <%= count %> </ h2 > </ body > </ html >
Read more

Query Strings

Image
 req.query() - used to get the query string(searched) app . get ( "/search" ,( req , res ) => {   let { q } = req . query ;   // console.log(q);   if ( ! q ){     res . send ( "<h1>nothing searched</h1>" );   }   res . send ( `<h1>search results for ${ q } </h1>` ); });
Read more