Develop applications that use programmatic security

For some applications, declarative security is not sufficient to express the security model of the application. Use this topic to develop applications that use programmatic security.

Overview

• Development

• Assembly

• Deployment

Most of the security for an application is configured during the assembly stage. The security that is configured during the assembly stage is called declarative security because the security is declared or defined in the deployment descriptors. The declarative security is enforced by the security runtime. For some applications, declarative security is not sufficient to express the security model of the application. For these applications, you can use programmatic security.

Procedure

1. Develop secure Web applications. For more information, see Developing with programmatic security APIs for Web applications.

2. Develop servlet filters for form login processing. For more information, see Developing servlet filters for form login processing.

3. Develop form login pages. For more information, see Customizing Web application login.

4. Develop enterprise bean component applications. For more information, see Developing with programmatic APIs for EJB applications.

5. Develop with Java Authentication and Authorization Service to log in programmatically. For more information, see Developing programmatic logins with the Java Authentication and Authorization Service.

6. Develop your own Java 2 security mapping module. For more information, see Configuring programmatic logins for Java Authentication and Authorization Service.

7. Develop custom user registries. For more information, see Developing standalone custom registries.

8. Develop a custom interceptor for trust associations.

Related concepts

Related tasks

Related Reference