Securing AquaLogic Service Bus in a Production Environment

To prepare an AquaLogic Service Bus installation for production, you must pay special attention to your security needs. The following list outlines some of the tasks you need to perform:

Read and follow the guidelines in Securing a Production Environment in the WebLogic Server documentation.
Create user accounts for the AquaLogic Service Bus administrators and assign them to one or more of the following groups as appropriate: IntegrationAdministrators, IntegrationOperators, IntegrationMonitors, and IntegrationDeployers. For more information, see “Role-Based Access in AquaLogic Service Bus Console” under “Overview of Security Configuration” in Security Configuration in Using the AquaLogic Service Bus Console.
In your file system, configure access control to the directory that contains AquaLogic Service Bus configuration data. This is the sbconfig directory under the domain root. For example:

C:\bea\user_projects\domains\base_domain\alsb\config

In your file system, configure access control to the directories used by the FTP, SFTP, file, and email transports.
If necessary, configure access control to the JMS resources used by your AquaLogic Service Bus installation.

Undeploying the Service Bus (SB) Resource

AquaLogic Service Bus provides a resource servlet (BEA_HOME/servicebus/lib/sbresourceWar/sbresource.war) that is used to expose the resources registered in AquaLogic Service Bus. The resources registered with AquaLogic Service Bus include:

WSDL (a WSDL registered as a resource in AquaLogic Service Bus)
Schema
MFL
WS-Policy
WSDL (an effective WSDL with resolved policies and port information for a proxy service—this effective WSDL is available if the proxy service was created using a WSDL).

However, this servlet provides anonymous HTTP access to metadata, and as such it may be considered a security risk in some high-security environments.

If you do not want the AquaLogic Service Bus resources to be available anonymously via HTTP, you can set security roles on sbresources.war to control access to it, or completely undeploy the resource.

Protection of Temporary Files With Streaming body Content

As described in The Message Context Model, for processing message content, you can specify that the ALSB pipeline streams the content rather than loading it into memory. When you enable content streaming for a proxy service, you specify whether to buffer the streamed content to memory or a disk file as an intermediate step during the processing of the message.

To lock-down your ALSB domain, set the com.bea.wli.sb.context.tmpdir java system property to specify where these temporary files will be written.

For more information see the file access permission and file system recommendations in Securing a Production Environment in the WebLogic Server documentation.

Security Guide

Securing AquaLogic Service Bus in a Production Environment

Undeploying the Service Bus (SB) Resource

Protection of Temporary Files With Streaming body Content