Chapter 11. Securing your application

In this chapter:

  • Ensuring that only authenticated users can edit a list
  • Accessing discount-editing functionality

In the previous few chapters, we looked at custom components while we developed the discount-list example. In this chapter, we’ll take that example and secure it. The discount list has a function to edit discounts, which is currently available to all users of the web application. We’ll change that so only specific users—administrators—can edit this list.

The first step in doing so is to ensure that users are who they say they are. This is called authentication. The simplest and most common form of authentication requires users to provide a username and password combination. This is what we’ll ...

Get Wicket in Action 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.