[prev in list] [next in list] [prev in thread] [next in thread]
List: jaxme-dev
Subject: [jira] [Created] (WSS-610) WSSecurityUtil.decodeAction misbehaving when sending NoSecurity
From: "Alexandru-Constantin Bledea (JIRA)" <jira () apache ! org>
Date: 2017-07-08 15:40:00
Message-ID: JIRA.13085697.1499528381000.200053.1499528400429 () Atlassian ! JIRA
[Download RAW message or body]
Alexandru-Constantin Bledea created WSS-610:
-----------------------------------------------
Summary: WSSecurityUtil.decodeAction misbehaving when sending NoSecurity
Key: WSS-610
URL: https://issues.apache.org/jira/browse/WSS-610
Project: WSS4J
Issue Type: Bug
Components: WSS4J Core
Reporter: Alexandru-Constantin Bledea
Assignee: Colm O hEigeartaigh
The decode method from WSSecurityUtil doesn't appear to do the right thing when \
sending NoSecurity.
If we're sending for instance "UsernameToken NoSecurity Signature" we're getting back \
[1] From my point of view, it should probably return [1, 0, 2].
It seems like the person who wrote that code wanted NoSecurity to override any other \
security policy, in that case it should probably return just [0], but stopping at \
what we already parsed up to now and not including NoSecurity doesn't seem to be the \
correct behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic