Developing secured applications

Why and when to perform 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 described in the Java 2 Enterprise Edition (J2EE) specification. An application goes through three stages before it is ready to run:

Most of the security for an application is configured during the assembly stage. The security 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 run time. For some applications, declarative security is not sufficient to express the security model of the application. For these applications, you can use programmatic security.

Steps for this task

  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 Developing form login pages.
  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 application logins for Java Authentication and Authorization Service.
  7. Develop custom user registries.
    For more information, see Developing custom user registries.
  8. [5.0 only][Version 5.0.1][Version 5.0.2]Develop a custom interceptor for trust associations.
    For more information, see Developing a custom interceptor for trust associations

Related concepts
Web component security
Enterprise bean component security
Programmatic login
Trust Associations
Java Authentication and Authorization Service
Java 2 Connector security
Custom user registries
Related reference
Example: Getting the Caller Subject from the Thread[Version 5.0.2 and later]
Example: Getting the RunAs Subject from the Thread[Version 5.0.2 and later]
Example: Overriding the RunAs Subject on the Thread
Example: User revocation from a cache[Version 5.0.2 and later]



Searchable topic ID:   tsecdesign
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_design.html

Library | Support | Terms of Use | Feedback