You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Fred Dushin (JIRA)" <ji...@apache.org> on 2006/10/06 21:01:19 UTC
[jira] Created: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
[PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
-----------------------------------------------------------------------------------------------------
Key: WSS-57
URL: http://issues.apache.org/jira/browse/WSS-57
Project: WSS4J
Issue Type: Improvement
Reporter: Fred Dushin
Assigned To: Davanum Srinivas
Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
* the action performed (signature or encryption)
* a representation of the received identity, encapsulated in a java.security.Principal
* the recieved certificate, in the case of singing
* the operative SAML assertion (if applicable)
* any timestamp information (if applicable)
* a set of wsu:ids, representing the signed elements (
* the signature
* the signature confirmation
It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
A patch will be submitted separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Dushin updated WSS-57:
---------------------------
Attachment: wss-57.patch
Updated patch, built off the latest trunk (revision 521556)
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: wss-57.patch, WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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] Commented: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-57?page=comments#action_12440611 ]
Davanum Srinivas commented on WSS-57:
-------------------------------------
Sounds neat!
-- dims
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: http://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Updated: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Dushin updated WSS-57:
---------------------------
Attachment: WSS-57.patch
Apologies -- this patch has been sitting around on my disk for a long time!
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Dushin updated WSS-57:
---------------------------
Attachment: WSS-57.patch
Apologies -- this patch has been sitting around on my disk for a long time!
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Fred Dushin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Dushin updated WSS-57:
---------------------------
Attachment: wss-57.patch
Updated patch, built off the latest trunk (revision 521556)
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: wss-57.patch, WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruchith Udayanga Fernando resolved WSS-57.
------------------------------------------
Resolution: Fixed
Applied the patch - Thanks Fred.
http://svn.apache.org/viewvc?view=rev&rev=522256
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: wss-57.patch, WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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] Commented: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/WSS-57?page=comments#action_12440611 ]
Davanum Srinivas commented on WSS-57:
-------------------------------------
Sounds neat!
-- dims
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: http://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-57) [PROPOSAL] Add additional information to
WSSecurityEngineResult, to enhance enforce-ability of policy
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruchith Udayanga Fernando resolved WSS-57.
------------------------------------------
Resolution: Fixed
Applied the patch - Thanks Fred.
http://svn.apache.org/viewvc?view=rev&rev=522256
> [PROPOSAL] Add additional information to WSSecurityEngineResult, to enhance enforce-ability of policy
> -----------------------------------------------------------------------------------------------------
>
> Key: WSS-57
> URL: https://issues.apache.org/jira/browse/WSS-57
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Assigned To: Davanum Srinivas
> Attachments: wss-57.patch, WSS-57.patch
>
>
> Currently, the WSSecurityEngineResult type yeilds the following information, when returned after processing security headers in a message:
> * the action performed (signature or encryption)
> * a representation of the received identity, encapsulated in a java.security.Principal
> * the recieved certificate, in the case of singing
> * the operative SAML assertion (if applicable)
> * any timestamp information (if applicable)
> * a set of wsu:ids, representing the signed elements (
> * the signature
> * the signature confirmation
> It would be useful to also get a reference to the DOM elements that were signed or encrypted, as well.
> I would propose that instead of defining a *Results object, we instead generalize the type to something like a Map, which has the advantage that we can add information through the returned structure without having to modify an otherwise potentially brittle type. All we then need to do is provide constants for the tags we use to select these values from the map, and document, accordingly.
> A patch will be submitted separately.
--
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