See wam Menu

Overview of Programming Web Apps Using WAM

You can use information provided by WAM to make fine-grained access control decisions in your web apps.

In other words, users with distinct identities, roles, account information, login locations, login times, and so forth may be presented with different web app user interfaces and application functionality. The difference can range from dynamically changing a button or image based on user values to populating fields to denying access to a resource.

WAM is integrated more tightly with some environments. For example, all web app programming environments (JSP/servlet, ASP.NET, PHP, and PERL, for example) will have access to WAM secure request headers. However, only J2EE containers with WAM web agents will have access to the J2EE servlet security APIs.

Who Should Read This Section

This section provides a brief tutorial on the WAM security services and resources available to web app programmers. You should have an understanding of web app programming, as well as a basic knowledge of the HTTP protocol. A knowledge of Java is required if you need to use the WAM APIs to extend the WAM server.

Have a Question?

Have a how-to question? Seeing a weird error? Contact us.

Found a bug? Submit a support ticket.

Have a product idea or request? Share it with us in our Ideas Portal.