[
https://issues.apache.org/jira/browse/WSS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated WSS-103:
------------------------------------
Attachment: wss4j_bst.patch
Please apply the attached patch for this problem.
> BinarySecurityToken processor does not allow for custom token types
> -------------------------------------------------------------------
>
> Key: WSS-103
> URL: https://issues.apache.org/jira/browse/WSS-103
> Project: WSS4J
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Assignee: Ruchith Udayanga Fernando
> Priority: Minor
> Attachments: wss4j_bst.patch
>
>
> The class BinarySecurityTokenProcessor does not allow for custom token types,
> but throws an exception if the token is anything other than a PKIPathSecurity
> or an X509Certificate token. This does not allow for a scenario that an
> inbound message has a signed custom BST, where the role of WSS4J is to
> perform the signature validation, but to delegate the processing of the
> (custom) BST to some custom code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]