[
http://jira.jboss.com/jira/browse/JBWS-1188?page=all ]
Thomas Diesler updated JBWS-1188:
---------------------------------
Fix Version/s: jbossws-1.0.5
(was: jbossws-1.0.4)
Rescheduled due to inactivity. Code freeze was on 17-Oct-2006.
Please communicate your intentions so we can act appropriately in a timely manner.
Past jira freeze, issues that are scheduled for a particular release past jira freeze
should be fixed and not allowed to be sliped. Jira freeze was on 18-Sep-2006.
If this is not possible for unforseen reason this must be escalated to the release
manageer in a timely manner.
If we don't stick to these simple rules, our release planing becomes meaningless.
Relax requirement for wsu:id for UsernameToken
----------------------------------------------
Key: JBWS-1188
URL:
http://jira.jboss.com/jira/browse/JBWS-1188
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ws-security
Affects Versions: jbossws-1.0.3
Reporter: Darran Lofthouse
Assigned To: Darran Lofthouse
Fix For: jbossws-1.0.5
The JBossWS UsernameToken implementation is mandating that the wsu:id attribute is
present on incomming requests.
Some thirdparty web services stacks being used as clients to JBossWS do not send the ID
so we are rejecting the request. Additionally we do not actually use the id anywhere
anyway.
The requirement for the id should be relaxed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira