[
https://issues.apache.org/jira/browse/RAMPART-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18147861#comment-18147861
]
Robert Lazarski commented on RAMPART-463:
-----------------------------------------
That's a Rampart bug, not WSS4J. WSS4J does treat the missing
Type as PasswordText when it verifies the password, but it leaves
getPasswordType() null, and Rampart's own policy check
afterwards assumed a type was always present.
Fixed on master (efd2a389): PolicyBasedResultsValidator now reads
a missing or empty Type as PasswordText. It will be in the next
release.
Until then, since you already subclass
PolicyBasedResultsValidator, you can override
handleSupportingTokens in your validator to work around it on
2.0.0.
The workaround line rests on the stack trace in the report, where
their validator extends PolicyBasedResultsValidator; drop it if
you'd rather not suggest patching around a release.
> Conformance to WS-I Basic Security Profile
> ------------------------------------------
>
> Key: RAMPART-463
> URL: https://issues.apache.org/jira/browse/RAMPART-463
> Project: Rampart
> Issue Type: Question
> Components: rampart-core
> Affects Versions: 2.0.0
> Reporter: Andreas Martens
> Assignee: Robert Lazarski
> Priority: Major
>
> Does Rampart prioritise Basic Security Profile Version 1.1 over WS-Security
> 1.1?
> Loaded question.
> On the Rampart homepage it says
> {quote}Rampart implements the following specifications:
> {quote} *
> {quote}WS - Security 1.0{quote}
> *
> {quote}WS - Security 1.1{quote}
> *
> {quote}WS - Secure Conversation - February 2005{quote}
> *
> {quote}WS - Security Policy - 1.1 - July 2005{quote}
> *
> {quote}WS - Security Policy - 1.2{quote}
> *
> {quote}WS - Trust - February 2005{quote}
> *
> {quote}WS - Trust - WS-SX specification{quote}
> *
> {quote}SAML Specification - 1.1{quote}
> *
> {quote}SAML Specification - 2.0{quote}
> But!
> Try to put in a message that conforms to WS-Security UsernameToken Profile
> 1.1
> [https://docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-pr-UsernameTokenProfile-01.htm,]
> which explicitly states:
> {quote}/wsse:UsernameToken/wsse:Password/@Type
> This optional URI attribute specifies the type of password being provided.
> The table below identifies the pre-defined types (note that the URI fragments
> are relative to the URI for this specification).
> {quote}
> if we don't include the Type in the header, Rampart raises a Fault,
> explicitly mentioning
> {quote}R4201 Any PASSWORD MUST specify a Type attribute.
> {quote}
> Which is a requirement from Basic Security Profile Version 1.1
> ([https://www.ws-i.org/profiles/basicsecurityprofile-1.1.html#Password).]
>
> Normally I'd be fine with it, but we've received complaints :(
> Can we have clarification whether this is _intended_ behaviour?
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]