You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2008/04/01 16:56:26 UTC
[jira] Created: (WSS-103) BinarySecurityToken processor does not
allow for custom token types
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
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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-103) BinarySecurityToken processor does not
allow for custom token types
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-103.
-------------------------------------
Resolution: Fixed
Thanks Fred.
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-103) BinarySecurityToken processor does not
allow for custom token types
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Closed: (WSS-103) BinarySecurityToken processor does not
allow for custom token types
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-103.
-----------------------------------
> 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: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org