Last Modified : $Date: 2009/05/27 16:21:57 $ by $Author: ritzmann $
This document provides a list of
This document covers the following topics:
Updated: May 26, 2009
Updated: May 26, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: 26th May, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: May 26, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: 27th May, 2009
New in this release
Fixed in this release
Known Issues
Interoperability Feature |
Status |
Remark |
---|---|---|
Issue 710 :
<sp:IncludeTimestamp> is a binding level assertion in
WS-SecurityPolicy. This prevents a clean approach to having some secure
and some non-secure methods in a WebService |
Scheduled for Metro 1.3
release. |
|
Issue 715:
Security Failures in AIX when using TripleDES Algorithm |
Scheduled for Metro 1.5 release. | |
"" URI Reference not supported in Signature |
Need to support empty URI Reference in Signature Issue#269 |
Will be supported in a future release |
Returning of SOAP fault : Negative tests with Mismatched client and server policies |
SOAP Fault not returned: Different Algorithm suites used by Service Consumer/Provider. Issue#22 on IssueTracker |
Will be supported in a future release. |
EncryptedParts in SupportingTokens |
EncryptedParts in SupportingTokens assertion in message policy
does not work |
Need a clarification from the WS-SecurityPolicy Specification as to whether Encrypted Parts inside SupportingTokens makes sense. |
SecurityPolicy:sp:AlgorithmSuite/wsp:Policy/ |
SecurityPolicy:sp:AlgorithmSuite/wsp:Policy/sp:SoapNormalization10
assertion causes deploy failure Issue#16 |
Feature Not Implemented |
SecurityPolicy: sp:AlgorithmSuite/wsp:Policy/sp:XPath10 assertion |
SecurityPolicy: sp:AlgorithmSuite/wsp:Policy/sp:XPath10 assertion causes deploy failure Issue#15 |
Feature Not Implemented |
SecurityPolicy: sp:AlgorithmSuite/wsp:Policy/sp:XPathFilter20 assertion |
SecurityPolicy: sp:AlgorithmSuite/wsp:Policy/sp:XPathFilter20 assertion causes deploy failure Issue#14 |
Feature Not Implemented |
ProtectToken with X509Token and
RequireDerivedKeys |
The client is uanble to
generate the request soap message and the exception thrown is:
javax.xml.crypto.URIReferenceException:Issue#76 |
Will be fixed in a future
release. Note that WCF RTM does not support sp:ProtectTokens assertion |
Security with List data type
dropping xs namespace declaration |
Issue#971 | This issue is now fixed for Sign, and Sign + Encrypt scenario.
It issue still exists for plain Encryption scenario. The workaround should be to use Sign+Encrypt if encryption is required,
or use non-optimized security. |
Security for JSR 109 WebServices does not work with V3-Prelude |
GlassFish V3 Prelude does not have WS-Security support for JSR 109 WebService |
Feature requests not implemented in this release
WS-SecurityPolicy |
Assertion |
Remark |
5.3.1 |
RequiredElements |
Will be supported in a future release |
6.1.1 |
TokenInclusion |
includeTokenPolicy=Once
is NOT supported, except for the case of Keberos Tokens where Once is the only supported value,
Always, AlwaysToRecipient and Never are supported (refer known Issue# 19) |
6.3.1 |
UsernameToken |
Only <sp:UsernameToken10> is supported in this release, <sp:UsernameToken11> |
6.3.3 |
X509Token |
Only <sp:WssX509V3Token10> is supported in this release.
|
6.3.9 |
RelToken |
No Plan for supporting this token. |
6.3.6 |
SecurityContextToken |
No Plan for supporting this token |
6.3.5 |
SpnegoContextToken |
Will be supported in a future release |
7.1/8.1 |
AlgorithmSuite |
All algorithms are supported with
the exception of algorithms under Asymmetric KeyWrap. sp:AlgorithmSuite/wsp:Policy/sp:XPathFilter20
assertion causes deploy failure (refer known Issue#14) |
7.5 |
Token Protection |
Token Protection in cases where includeTokenPolicy="Never" or in cases where the Token is not in the Message, is not handled correctly yet (refer known Issue# 76, 206). |
9.2 |
SignedSupportingTokens |
The runtime will not be able to sign the supporting
token in cases where the Token is not in the Message (such as for
includeTokenPolicy=Never/Once). |
9.4 |
SignedEndorsingSupportingTokens |
The runtime will not be able to sign the supporting token in
cases where the Token is not in the Message (such as for
includeTokenPolicy=Never/Once). |
10.1 |
WSS10 Assertion |
Everything is supported with the Exception of <sp:MustSupportRefEmbeddedToken>. |
10.2 |
WSS11 Assertion |
Everything is supported with the Exception of <sp:MustSupportRefEmbeddedToken>. |
11.1 |
Trust10 Assertion |
MustSupportClientChallenge, MustSupportServerChallenge are not supported in this release. |
Updated: May 26, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: May 26, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: May 26, 2008
New in this release
Fixed in this release
Known issues
Feature | Status/Workaround |
---|---|
"WSTXServices" is listed as a deployed web service in the NetBeans 5.5.1 SJSAS admin interface (Runtime -> SJSAS -> Applications -> Web Applications) |
This isn't an issue, per se, just an FYI so users are not confused when they see the WS-TX system app listed in the NB UI. It is supposed to be hidden (and it is in NB 6). Users can attempt to undeploy the app, but the AS prevents this operation from happening. |
issue 717: Ejb web service deployment fails on AIX. |
Seeing this error during deployment of some TX SQE functional tests only on AIX:
|
issue 718: TX interop S->M on AIX, Error on HTTP request: 500 Internal Error. |
Seeing this error during TX interop S->M on AIX :
|
Issue 723 |
There is a regression causing that TX context does not get initialized in certain cases. The PolicyMap that is parsed second time (from the WSDL) does not contain the same, correct data. There is a problem in marshalling Policy data into WSDL during WSDL creation. |
Feature requests not implemented in this release
Updated: 26th May, 2009
New in this release
Fixed in this release
Known issues
Feature |
Status/Workaround |
---|---|
Security settings are not supported with GlassFish v3 | Metro 2.0EA does not yet support Security with JSR109 deployment on GlassFish v3, thus security settings in QoS dialog are not supported. The fix is targeted to METRO 2.0 FCS release. |
To enable Microsoft WCF <-> Java interoperability, an 'action=operationName' attribute needs to be specified on each operation. | The sample code should look like this:
|
Package rename refactoring does not modify WSIT configuration file name | When renaming a package that contains a web service class, the WSIT config file is not renamed accordingly. As a work-around, you can manually change the name of the configuration file under the Web Pages->WEB-INF node to wsit.<newpkgname>.xml. See NetBeans issue 105287 |
Updated: May 27, 2009
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release
Updated: May 27th, 2009
New in this release
Fixed in this release
Known issues
Interoperability Feature |
Status/Workaround |
---|---|
SupportingTokens assertion |
EncryptedParts in SupportingTokens assertion in message policy does not work |
The following security policy assertions cause a deploy failure:
|
Feature requests not implemented in this release
Updated: May 26, 2008
New in this release
Fixed in this release
Known issues
Feature requests not implemented in this release