
Today, every application must take security into account. While security covers a wide range of areas, this article focuses on application security and more specifically, user authentication and authorization. Authentication verifies that the user is who he says he is, while authorization verifies that the current user has permission to do what he wants to do.
To illustrate these concepts, this article uses a sample Flex application that manages and displays lists of books. This Flex client uses BlazeDS to talk to a server that runs another application built using the Spring framework. The sample is a complete application that demonstrates the many facets of securing an application that uses Flex on the client side.
One of the modules the Spring framework provides is Spring Security (formerly known as Acegi). The Spring Security module takes care of the authentication as well as the authorization of remote services. I am not going to focus on the Spring integration since that has already been covered by Sébastien Arbogast in a series of articles on Adobe Developer Connection titled "The Flex, Spring, and BlazeDS full stack".
A basic understanding of the Flex event model, Java web applications, and the Spring framework is required.

This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.
Jettro Coenradie is a software architect for the Dutch company JTeam B.V. Jettro likes to combine innovation with practical use. Last year, Jettro's focus was on security, OSGi, Spring framework, software engineering best practices, and, of course, Flex.