Cookies authentication
Download as PPTX, PDF0 likes203 views
The document outlines the concept of cookies and their role in web authentication, explaining how they enable web servers to remember users and their preferences. It describes the scope of a proposed system to authenticate cookies and verify user information, using PHP programming and a dynamic database. The document also details the benefits of cookie authentication, including personalization and ease of use, alongside a proposed model and algorithm for user login and authentication processes.
![PROPOSED MODEL
Proposed model
We have proposed a model for the implementation of the project
which is given below. Firstly, we enter the URL for the login
process then it will be sent to the server and sends the message
back to the server. The authenticate script takes the name and
given password. Now this name and password will be compared
with the name and password stored in the database and then
carried out the authentication process [6]. This is also clearly
explaining in the below flowchart.](https://image.slidesharecdn.com/cookiesauthentication-181203071452/85/Cookies-authentication-10-320.jpg)
Cookies authentication
- 2. DEFINITION OF NEED • A Web server has no memory so the hosted Web site that the user is visiting transfers a cookie file of the browser on the computer's hard disk so that the Web site can remember who is the user and the user preferences. This message exchange allows the Web server to use this information to present the user with customized Web pages. • Cookies allow online marketers and retailers deliver that personable experience with their customers.
- 3. DEFINITION OF NEED • Authentication cookies are the most common method used by web servers to know whether the user is logged in or not, and which account they are logged in with • For example, the Google search engine once used cookies to allow users (even non-registered ones) to decide how many search results per page they wanted to see.
- 4. SCOPE OF PROJECT •Our system authenticates the cookies. •Our system verifies information provided by user. •It grants access to authorized user. •It denies access to unauthorized users.
- 5. ASSUMPTIONS MADE • We have assumed testing data as client’s user id and password only. • We have used demo number of authorized clients. • Our database is dynamic, where we can edit number of fields.
- 6. SOLUTION APPROACH 1. We first researched about cookies. 2. We found reasons to authenticate it. 3. We discussed among group members and formed a flowchart to approach solution. 4. We used php for coding our system. 5. We also created a database to store information.
- 7. WHAT ARE COOKIES ? • A cookie is a text file that a website stores on a client’s computer to maintain information about the client during and between browsing sessions. • Are designed to hold a small amount of data specific to a particular client and website, and can be accessed either by the web server or the client computer • Useful for: • Shopping carts • User communities • Personalized sites • Not recommended for storing sensitive data • Store a unique identification string that will match a user held securely in a database
- 8. COOKIES AUTHENTICATION • In web services, the cookie is authenticated by providing the user name and password. • In addition, some web services may ask the security question that was created during the sign up phase to make the user account more secure.
- 9. BENEFITS OF COOKIES AUTHENTICATION • Cookies give customized experience and helps user. • Cookies are simple to use and implement • It occupies less memory, and these are stored in clients computer which saves memory burden on server. • Cookies can be set to expire as per requirement. We can assign it for particular time-frame.
- 10. PROPOSED MODEL Proposed model We have proposed a model for the implementation of the project which is given below. Firstly, we enter the URL for the login process then it will be sent to the server and sends the message back to the server. The authenticate script takes the name and given password. Now this name and password will be compared with the name and password stored in the database and then carried out the authentication process [6]. This is also clearly explaining in the below flowchart.
- 11. PROPOSED MODEL CONTINUED Start Is user valid ? Verify user Process request end
- 12. ALGORITHM 1. Start 2. Create a form to input user-id and password. 3. Send the entered user-id and password to the server. 4. Validate and compare the user-id and password a. Goto step 2 if not valid b. Goto step 5 if valid
- 13. ALGORTHM CONTD…. 5. Display the successful message 6. Ask user for next request and continue. 7.Stop
- 14. FLOWCHART MAIN
- 15. SCRENSHOT OF LOGIN FORM CREATED
- 16. SCREENSHOT FOR DIFFERENT INPUTS
- 17. SCREENSHOTS OF VALID AND INVALID LOGIN ATTEMPTS
- 18. DEMO