|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86-64
Part Number E14770-25
This chapter describes issues associated with Web services security and administration, including Oracle Web Services Manager. It includes the following topics:
In this release, multibyte user credentials are not supported for the wss_http_token_* policies. If multibyte user credentials are required, use a different policy, such as wss_username_token_* policy. For more information about the available policies, see Appendix B "Predefined Policies" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.
It is recommended that you import custom policies before attaching and deploying them to a service application.
If you deploy an application with policies that do not exist in the Metadata Store (MDS), and subsequently import the policies, you need to restart the server for the policy attachment count to be updated.
When performing a bulk import of policies to the MDS repository, if the operation does not succeed initially, retry the operation until the bulk import succeeds.
For the most part, this can occur for an Oracle RAC database when the database is switched during the metadata upload. If there are n databases in the Oracle RAC database, then you may need to retry this operation n times.
For more information about bulk import of policies, see "Migrating Policies" in the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.
If you attach a policy to a client, override policy configuration values, and subsequently detach the policy, the policy configuration override values are not deleted. When attaching new policies to this client, ensure that you review the policy configuration override values and update them appropriately.
When the connections.xml file is changed after deployment using the AdfConnection MBean, the complete connection is saved as a customization. This means that changes to the connection in a redeployed application are overwritten by the customization.
When you use Fusion Middleware Control to make changes to an application's connections.xml file after deployment, a new connections.xml file is created as a customization and stored in the MDS repository. This customization persists for the life of the application. Therefore, if you redeploy the application, the customized connections.xml file continues to be applied as a customization on the application.
To allow the redeployed application's connections.xml file to be applied without the prior customization (from Fusion Middleware Control), you must explicitly remove the
connections.xml customizations from the MDS repository.
For example, if you deploy an application with a Web services data control, then use Fusion Middleware Control to attach the 'username token client policy', and subsequently detach the policy. Then, you return to JDeveloper to edit the application and attach the 'http token client policy', and redeploy the application. When you view the application using Fusion Middleware Control, you see that it is not using the 'http token client policy' that you attached. That is because it is using the customized connections.xml file that you previously created using Fusion Middleware Control.
If you remove the connections.xml customizations from the MDS repository, the application will use the its own connections.xml file.
The following information is supported in English only in this release of Oracle Enterprise Manager:
All fields in the policy and assertion template except the
If using the
?orawsdl browser address, the
In the System MBean browser, the Description field in the
When WLST is used to import a security policy, be aware that the same policy may be repeatedly imported.
For ADF DC applications, the identity extension in a WSDL (for example, the certificate published in the WSDL), cannot be used as a recipient certificate for message protection policies. Instead, either the recipient key alias (declarative configuration override) or the default recipient key alias specified in the policy are used.
Within a JVM, the Kerberos acquire key works fine when there is only a single Web service principal. If there are additional Web service principals within the same JVM, the acquire key returns null. When a Web service and client exist in different JVMs, this is no longer an issue.
When a Managed Server is Two-way enabled SSL (for example, a SOA server hosting Oracle WSM Policy Manager over Two-way SSL) and the Administration Server hosting Fusion Middleware Control is correctly configured to access the Two-way SSL-enabled Managed Server, Fusion Middleware Control still does not list the Oracle WSM policies.
For Web services that have any input arguments bound to SOAP headers, the Test Web Service page in the Fusion Middleware Control console cannot show the message. Therefore, such operations cannot be tested with the Test Web Service page.
For example, if the input for a multi-part WSDL is viewed through Fusion Middleware Control, and one input argument is bound to a SOAP header, the composite instance fails with the following exception because the other part of the message was missing in the input:
ORAMED-01203:[No Part]No part exist with name "request1" in source message
To resolve such an issue, select XML View for Input Arguments and edit the payload to pass input for both parts of the WSDL.
The build label and date information on the Policy Manager Validation page represent the repository information and the version of the Policy Manager. The build label represents the Policy Manager build that populated the repository and the date is the date that the repository was last refreshed. If the repository is not refreshed during a sparse installation of Oracle Fusion Middleware 11gR1 PS2, the information will not change. Note that a typical installation of Oracle Fusion Middleware 11gR1 PS2 does not refresh the repository either.
In release 11g R1 (188.8.131.52.0), when you try to add or edit a trusted issuer from the Fusion Middleware Control console, then the
jps-config.xml file is incorrectly updated. As a workaround for this issue, Oracle recommends upgrading to 11g R1 Patch Set 2 (184.108.40.206.0).
Due to a new feature in 11g R1 Patch Set 2 (220.127.116.11.0), the "Shared policy store for Oracle Infrastructure Web services and WebLogic Server Web services", WebLogic Server Web services now utilize the Policy Manager by default to retrieve policies from the MDS repository. In Patch Set 1, WebLogic Server Web services used classpath mode by default.
After patching your Oracle Fusion Middleware 11g R1 software installation to Patch Set 2, if you have attached a custom Oracle WSM policy to a WebLogic Server Web service, you need to make sure your custom policy is stored in the MDS repository. Note that only custom policies in use need to be migrated. All seed policies will be available in the MDS repository out-of-the-box.
To migrate policies to the Metadata Services (MDS) repository, see "Maintaining the MDS Repository" in the Security and Administrator's Guide for Web Services.
If an empty subject is passed to a custom policy, it fails with a generic error. To work around this issue, you can create and set an
anonymousSubject inside the execute method of the custom step. For example:
javax.security.auth.Subject subject = oracle.security.jps.util.SubjectUtil.getAnonymousSubject(); context.setProperty(oracle.wsm.common.sdk.IMessageContext.SECURITY_SUBJECT,subject)
Note that in this example the context is of Type
If your Web services are already in Oracle Enterprise Repository (OER), then you should use the OER Exchange Utility to publish those Web services to the Oracle Service Registry.
In some cases, there can be a limitation when using custom Exactly-one policies. For a set of assertions within the exactly-one policy, if a request message satisfies the first assertion, then the first assertion gets executed and a response is sent accordingly. However, this may not be the desired behavior in some cases because the request may be intended for the subsequent assertions.
For example, you may have a client policy that has
Timestamp=ON and a service exactly-one policy that has a
wss11 username token with message protection assertions: the first has
Timestamp=OFF; the second has
Timestamp=ON. Therefore, the first assertion in the service exactly-one policy is not expecting the Timestamp in the request, yet the second assertion does expect it. In this case, the first assertion gets executed and the response is sent with no Timestamp. However, the client-side processing then fails because it expects the Timestamp that was sent in the request.
This limitation can exist with any cases where a client policy expects a greater number of elements to be signed and a service policy does not.
Fusion Middleware Control may display a false error message when verifying compatibility between Oracle WSM security polices and WebLogic Server security polices. This happens because some WebLogic Server security policies use the 2007 version of WSSP 1.2, while other policies use the 2005 version (early draft). The false incapability message occurs when using the Enterprise Manager to attach an Oracle WSM security client policy. Upon clicking the Check Services Compatibility button, a message states that the services are incompatible. However, this service interoperability use case works for both versions of WSSP 1.2.
During design time, the JDeveloper Wizard's option for Attaching Oracle WSM Policies to Web Service Clients might not return any compatible policies. This can occur due to one of the following reasons:
There are no compatible client policies corresponding to the service policies published in the WSDL.
In some cases, when you are trying to determine the compatible client policies in version 18.104.22.168 of JDeveloper running with Fusion Middleware Control Enterprise Manager that correspond to the service policies published in the WSDL of the Web service in version 22.214.171.124 or earlier.
Disable the Show only the compatible client policies for selection option in the JDeveloper Wizard. This will list all the client policies.
If Oracle WSM policies are attached to the Webs service, use the corresponding client policy. For example, if the service has the policy wss11_saml_or_username_token_with_message_protection_service_policy, it is safe to assume that wss11_saml_token_with_message_protection_client_policy or wss11_username_token_with_message_protection_client_policy will work at the client side.
If WSM policies are not attached to the Web service, refer to the Interoperability Guide for Oracle Web Services Manager for instructions on determinant the corresponding client policy and attaching it.
The following policy is new for this release, but is not documented: wss_saml_or_username_token_service_policy
This policy enforces one of the following authentication policies, based on whether the client uses a SAML or username token, respectively:
SAML token within WS-Security SOAP header using the sender-vouches confirmation type.
WS-Security UsernameToken SOAP header to authenticate users against the Oracle Platform Security Services configured identity store.
The policy contains the following assertions, as an OR group, meaning either type of policy can be enforced by a client:
For information about configuring the policy, see the configuration descriptions for oracle/wss10_saml_token_service_policy and oracle/wss_username_token_service_policy in Appendix B "Predefined Policies" section of the Oracle Fusion Middleware Security and Administrator's Guide for Web Services.
In this release of the Oracle Fusion Middleware Security and Administrator's Guide for Web Services, Appendix D "Schema Reference for Predefined Assertions" has not been updated to reflect the STS policies. This appendix will be updated in the next release.
A new property,
saml.enveloped.signature.required, is available when configuring wss_saml_token_bearer_over_ssl policies (both client and service). In previous releases, the SAML bearer token was unsigned by default. In the current release, the SAML bearer token is signed because the default value for the
saml.enveloped.signature.required property is
To retain the behavior of the previous release, set the
saml.enveloped.signature.required property to
false in both the client and service policies. The SAML bearer token is signed using the domain sign key, but it can be overridden using the
keystore.sig.csf.key property set in the bearer client policy.
The affected policies are: