Documentation ![]() |
Show me ![]() |
Tell me ![]() |
Guide me ![]() |
Teach me ![]() |
Refer to the detailed steps and reference | Watch a brief multimedia demonstration | View the presentation for an overview | Be led through the console pages | Perform the tutorial with sample code |
Approximate time: Varies | Approximate time: 3 to 5 minutes | Approximate time: 10 minutes+ | Approximate time: 1/2 hour+ | Approximate time: 1 hour+ |
Develop and deploy secure applications
These tasks involve securing your applications during development (optional, programmatic security), assembly (declarative security), and after deploying them on the application server.
--------------------------------------------------------------------------
Most of the security for an application is configured during the assembly stage. The security you configure 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.
Documentation
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Most of the security for an application is configured during the assembly stage. The security you configure 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.
Documentation
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Use any of the available methods to integrate message-level security into an application serving environment. Web services security for WebSphere Application Server is based on a set of standards that are included in the Web services security (WS-Security) specification. These standards address how to provide protection for messages that are exchanged in a Web services environment. The set of specification defines the core facilities for protecting the integrity and confidentiality of a message and provides mechanisms for associating security-related claims with the message.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Java 2 security is disabled by default, but is enabled automatically when global security is enabled. Your decision to use Java 2 security is independent of your decision to use J2EE role-based authorization. Java 2 security provides an extra level of access control protection on top of the J2EE role-based authorization and addresses the protection of system resources and APIs.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
If you plan to write a login module that adds information to the Subject of a system login, refer to this topic for the main Java Authentication and Authorization Service (JAAS) plug-in points for configuring system logins.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Applications access many resources for data access, messaging, mail, and other purposes.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Secure the Java DataBase Connectivity (JDBC) data sources and Java 2 Connector (J2C) resources that are used by applications to access data.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Secure the Java Message Service (JMS) resources that are used by applications to obtain messaging support.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Secure the application hosting environment
The counterpart of securing your applications before and after deployment is to secure the server hosting environment into which the applications are deployed.
--------------------------------------------------------------------------
Use the administrative console to assign users to administrative roles.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Scripting is a non-graphical alternative that you can use to configure and manage WebSphere Application Server. Use the WebSphere Application Server wsadmin tool to run scripts. The wsadmin tool supports a full range of product administrative activities.
Documentation
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Configuring global security applies to all applications running in the environment and determines whether security is used, the type of registry against which authentication takes place, and other values (many of which act as defaults).
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Configure the product to authenticate users against the local operating system user registry. The product provides and supports the implementation for Windows operating system registries, AIX, Solaris, z/OS (using the SAF interface) and multiple versions of Linux operating systems. The respective operating system APIs are called by the product processes or servers for authenticating a user and other security-related tasks, for example, getting user or group information.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Configure the product to authenticate users against a Lightweight Directory Access Protocol (LDAP) user registry. The product provides and supports implementation of most major LDAP directory servers, which can act as the repository for user and group information. These LDAP servers are called by the product processes or servers for authenticating a user and other security-related tasks, for example, getting user or group information. This support is provided by using different user and group filters to obtain the user and group information. These filters have default values that you can modify to fit your needs. The custom LDAP feature enables you to use any other LDAP server, which is not in the product-supported list of LDAP servers, for its user registry by using the appropriate filters.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
After you implement the UserRegistry interface, you can configure the product to use your custom user registry to authenticate users. Your custom user registry can be supplied by a external security provider to enable the provider's solution, or you can write your own customer user registry. You can configure the product to use the customer user registry to handle authentication of users.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
With single signon (SSO) support, Web users can authenticate once when accessing Web resources across multiple WebSphere Application Servers. Form login mechanisms for Web applications require that SSO is enabled.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Configure Common Secure Interoperability Version 2 (CSIv2) features including SSL client certificate authentication, message layer authentication, identity assertion, and security attribute propagation.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Configure the product to use an external security provider you have set up to work with WebSphere Application Server that can support J2EE authorization based on the Java Authorization Contract for Containers (JACC) specification.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Troubleshoot security problems
Troubleshoot several types of problems that are related to enabling or configuring security.
--------------------------------------------------------------------------
Troubleshoot several types of problems that are related to enabling or configuring security.
![]() |
![]() |
![]() |
![]() |
![]() |
--------------------------------------------------------------------------
Related concepts
Overview and new features for securing applications and their environment
welc6productov.html