WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Securing adapters

As part of the process for securing your WebSphere ESB environment, you need to secure any WebSphere Adapters used by WebSphere ESB.

Why and when to perform this task

Adapters are the mechanism by which applications communicate with Enterprise Information Systems (EISs). The information that is exchanged between an application and an EIS may be highly sensitive. It is important to ensure the security of this information transaction.

WebSphere Adapters enable managed, bidirectional connectivity between Enterprise Information Systems (EISs) and the modules and J2EE components supported by WebSphere ESB.

For inbound communication from adapters into WebSphere ESB, there is no authentication mechanism, because the J2C functions used for WebSphere Adapters lack inbound security support.

The entry from an adapter to WebSphere ESB always employs a service component architecture (SCA) export. The SCA export has to be wired to an SCA component, such as a mediation module or SCA Java component.

To secure adapters, define a runAs role on the component that is the target for the WebSphere Adapter export. This is done using the SCA qualifier SecurityIdentity during development (see the WebSphere Integration Developer Information Center for more information). When the component runs in WebSphere ESB, it does so under the identity defined in the runAs role.


Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\doc\tsec_adapters.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)