You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/02/06 04:05:59 UTC
[jira] Created: (ODE-509) Encrypted body with Axis2 1.4 or higher
Encrypted body with Axis2 1.4 or higher
---------------------------------------
Key: ODE-509
URL: https://issues.apache.org/jira/browse/ODE-509
Project: ODE
Issue Type: Improvement
Components: Axis2 Integration
Reporter: Alexis Midon
Assignee: Alexis Midon
If you're using Axis2 1.4 or higher, you cannot encrypt message bodies due to a regresstion in Axis2.
Actually the Security phase fails to decrypt the body (see AXIS2-4233 for details) because the targeted operation is not resolved yet. But meanwhile the operation name is resolved base on the name of the first element in the body. catch-22.
As of 02/5/2009, only ODE trunk is affectred by this issue. ODE 1.X uses Axis2 1.3.
No known workaround for this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-509) Encrypted body with Axis2 1.4 or higher
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-509:
-----------------------------
Issue Type: Bug (was: Improvement)
> Encrypted body with Axis2 1.4 or higher
> ---------------------------------------
>
> Key: ODE-509
> URL: https://issues.apache.org/jira/browse/ODE-509
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Reporter: Alexis Midon
> Assignee: Alexis Midon
>
> If you're using Axis2 1.4 or higher, you cannot encrypt message bodies due to a regresstion in Axis2.
> Actually the Security phase fails to decrypt the body (see AXIS2-4233 for details) because the targeted operation is not resolved yet. But meanwhile the operation name is resolved base on the name of the first element in the body. catch-22.
> As of 02/5/2009, only ODE trunk is affectred by this issue. ODE 1.X uses Axis2 1.3.
> No known workaround for this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-509) Encrypted body with Axis2 1.4 or higher
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon resolved ODE-509.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0
> Encrypted body with Axis2 1.4 or higher
> ---------------------------------------
>
> Key: ODE-509
> URL: https://issues.apache.org/jira/browse/ODE-509
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 2.0
>
>
> If you're using Axis2 1.4 or higher, you cannot encrypt message bodies due to a regresstion in Axis2.
> Actually the Security phase fails to decrypt the body (see AXIS2-4233 for details) because the targeted operation is not resolved yet. But meanwhile the operation name is resolved base on the name of the first element in the body. catch-22.
> As of 02/5/2009, only ODE trunk is affectred by this issue. ODE 1.X uses Axis2 1.3.
> No known workaround for this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-509) Encrypted body with Axis2 1.4 or higher
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672451#action_12672451 ]
Alexis Midon commented on ODE-509:
----------------------------------
The fix is to set the policy on the MessageContext in ODEAxisServiceDispatcher.
> Encrypted body with Axis2 1.4 or higher
> ---------------------------------------
>
> Key: ODE-509
> URL: https://issues.apache.org/jira/browse/ODE-509
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 2.0
>
>
> If you're using Axis2 1.4 or higher, you cannot encrypt message bodies due to a regresstion in Axis2.
> Actually the Security phase fails to decrypt the body (see AXIS2-4233 for details) because the targeted operation is not resolved yet. But meanwhile the operation name is resolved base on the name of the first element in the body. catch-22.
> As of 02/5/2009, only ODE trunk is affectred by this issue. ODE 1.X uses Axis2 1.3.
> No known workaround for this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.