Book Image

KnockoutJS by Example

By : Adnan Jaswal
Book Image

KnockoutJS by Example

By: Adnan Jaswal

Overview of this book

KnockoutJS By Example is a project-based guide that introduces the key features and concepts of knockout.js. It helps you create an application skeleton and a Hello World application. You will develop a To-Do list application that aims to show the basic features of knockout.js in action, such as data binding and observables, following which you will develop a dynamic online customer registration form that captures and validates customer information. This book will further walk you through developing a customer banking portal, which demonstrates the use of knockout.js with components such as navigation bars, tabs, carousels, master details view, panels, forms, and wizards. You will also discover how to use token-based authentication and authorization to secure the customer banking portal, and move on to creating an editable products grid with CRUD operations. Finally, you will explore how to use the Google Maps API with knockout.js. KnockoutJS By Example will not only leave you with a basic understanding of knockout.js fundamentals but also take you through some of the advanced features. It will help you get a web application up and ready instantly.
Table of Contents (17 chapters)
KnockoutJS by Example
Credits
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
Index

Authentication mechanisms


We developed the interaction with the server in the last two chapters. In this chapter, we will explore different mechanisms by which we can provide authentication to the end user and protect the RESTful API endpoints. We will also implement an authentication approach based on JSON Web Token (JWT) for our customer banking portal. The following is a brief introduction of top four authentication mechanisms:

  • Basic authentication: As the name suggests, this is the simplest mechanisms for protecting a RESTful endpoint or any web resource for that matter. It sends Base64 encoded username and password in the HTTP header and does not enforce any confidentiality protection. The username and password must be sent with every request. You can find the specifications for this mechanism on the Internet Engineering Task Force's website at http://tools.ietf.org/html/rfc1945#section-11.

  • OAuth 1.0a: This provides authentication without ever directly passing the username and password...