Security
In the last chapter, we talked about how to protect our customer's credit card number from being eavesdropped on as it traveled from their browser to our server. But what about protecting the information on the server itself?
After all, just because it's on our server doesn't mean we want to broadcast it to the world! I mean, you wouldn't want just anybody to pull up a list of credit card transactions you haven't processed yet. This process of identifying a user for access to specific information is called authentication, and there are several options we have for doing it.
The first option is actually something that we've already been doing: using a page that takes in a username and password. From there we can decide what content to ...
Get Active Server Pages 3.0 from Scratch now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
