This chapter contains the following sections:
Authentication and session management are handled differently depending on the integration method being used. When first installed, the Imaging Web Services are configured with no Oracle Web Service Manager security policies applied. When no security policies are applied, the services leverage either the HTTP Basic Authentication mechanism or username token authentication. Note that Basic Authentication, where user credentials (user ID and password) are transmitted in the web service HTTP message header mechanism is not very secure since the users credentials are not encrypted in any way unless a Secure Socket Layer (SSL) transport mechanism is used.]
If SSL is properly configured for the Imaging server instance, Imaging can be configured to force the use of SSL in all web service communicaton. This done by setting the Imaging configuration MBean RequireBasicAuthSSL to true. By default, it is false.
The RequireBasicAuthSSL setting only applies when no HTTP Basic Authentication is in use because no OWSM security policies have been applied.
When higher degrees of security are desirable, Imaging web services support the following Oracle Web Services Management (OWSM) security policies.
When applying a security policy to the Imaging web services, remember that the same policy must be applied to all of the web services with the exception of the DocumentContentService. The DocumentContentService is designed to use streaming MTOM that is incompatible with OWSM security policies. Security for DocumentContentService first requires a separate, stateful login through the LoginService, which does leverage OWSM security policy. (This information is primarily significant when making direct web services calls. The proper login sequence occurs automatically when using the native Java API.
Security policies are applied to Imaging web services from the WebLogic Server Administration Console using the following procedure.
Log in to Administration Console.
Click Deployments. The Summary of Deployments page is displayed.
Click the plus (+) icon next to imaging in the Name column of the Deployments table. The imaging deployment expands.
Select the web service. The setting page for the service is displayed.
Select the Configuration tab. The configuration tab becomes active.
Select the WS-Policy tab. The WS-Policy tab becomes active.
Click the web service port in the Service Endpoints and Operations column of the WS-Policy Files Associated With This Web Service table. The Configure the Policy Type for a Web Service page is displayed.
Ensure OWSM is selected and click Next. Note that WebLogic polices are not supported. The Configure a WebService Policy page ID displayed.
Choose a supported service policy from the Available Endpoint Policies field. Supported polices are listed in the section "Providing SSL Communication for Basic Authentication".
Click the right arrow to move the selected policy to the Chosen Endpoint Policies field. Note that only one security policy should be selected.
Click Finish. The Save Deployment Plan Assistant page is displayed.
Click OK to save the deployment plan.
Repeat step 4 for each web service except DocumentContentService until the same policy is applied for all services.
Click Deployments to return to the Deployments page.
Enable the check box next to imaging in the Name column of the Deployments table and click Update. The Update Application Assistant page is displayed with the new deployment plan specified next to Deployment plan path.
Click Finish. The new policies are applied and the deployment updated.
When OWSM security policies are applied to the Imaging web service, Java API code must use the WsmUserToken class to login rather than the BasicUserToken class. The WsmUserToken class is a helper class for configuring OWSM client side security polices, including a set of static constants for setting the correct client side policy. Depending on the policy being used, addition configuration setting may be required as well. Refer to OWSM document for complete details on the meaning of the various configuration options.
The code fragments in Example 3-1 demonstrate possible usages of the WsmUserToken class for various policy types.