-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.1
-
JDK 6
JBoss 5.1.0 jdk 6
Windows XP
-
-
Release Notes
-
Low
-
-
Documented as Resolved Issue
I am filing this bug after discussing http://community.jboss.org/message/540669
Nonce is not decoded when encoding type is Base64.
UsernameToken has this piece of code:
String encodingType = elem.getAttribute("EncodingType");
if (encodingType != null && encodingType.length() > 0 && !Constants.BASE64_ENCODING_TYPE.equalsIgnoreCase(encodingType))
throw new WSSecurityException("Unsupported nonce encoding type: " + encodingType);
encodingType is not used anywhere else.
In UsernameTokenCallback.java there is the need to decode nonce, so, something like:
String nonce = (String)info.getInfo(NONCE);
if (nonce != null) {
try
catch (IOException e)
{ // ignore exceptions }}
need to be added to UsernameTokenCallback.java
- blocks
-
JBPAPP-6268 Release and upgrade JBossWS Native for EAP 5.1.2
- Closed
- incorporates
-
JBWS-3014 JBossWS does not decode Nonce
- Closed
- is cloned by
-
JBWS-3014 JBossWS does not decode Nonce
- Closed
- is related to
-
JBWS-2640 UsernameToken does not correctly handle "Created" element from wsse:Security soap header
- Closed