WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Developing 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.

About this task

IBM WebSphere Application Server provides security components that provide or collaborate with other services to provide authentication, authorization, delegation, and data protection. WebSphere Application Server also supports the security features that are described in the Java 2 Platform, Enterprise Edition (J2EE) specification. An application goes through three stages before it is ready to run:
  • 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 custom user registries .
  8. Develop a custom interceptor for trust associations.



Sub-topics
Protecting system resources and APIs (Java 2 security)
Developing with programmatic security APIs for Web applications
Developing with programmatic APIs for EJB applications
Related concepts
Web component security
Trust associations
Java Authentication and Authorization Service
J2EE connector security
Related tasks
Developing programmatic logins with the Java Authentication and Authorization Service
Securing enterprise bean applications
Developing extensions to the WebSphere security infrastructure
Related reference
Customization of a server-side Java Authentication and Authorization Service authentication and login configuration
J2C principal mapping modules
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_design.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)