You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Keith Godwin Chapman (JIRA)" <ji...@apache.org> on 2008/07/11 05:57:31 UTC
[jira] Created: (RAMPART-184) Secure conversation does not when
over HTTPS when a CustomHTTPSProtocol handler is specified
Secure conversation does not when over HTTPS when a CustomHTTPSProtocol handler is specified
--------------------------------------------------------------------------------------------
Key: RAMPART-184
URL: https://issues.apache.org/jira/browse/RAMPART-184
Project: Rampart
Issue Type: Bug
Reporter: Keith Godwin Chapman
Assignee: Ruchith Udayanga Fernando
Secure conversation does not when over HTTPS when a CustomHTTPSProtocol handler is specified. Axis2 client API lets you set a property (HTTPConstants.CUSTOM_PROTOCOL_HANDLER) on the messageContext to set a CustomHTTPSProtocol handler. Rampart does not copy this over to the messageContext when sending out the request to obtain a security token.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RAMPART-184) Secure conversation does not work
over HTTPS when a CustomHTTPSProtocol handler is specified
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandana Mihindukulasooriya reassigned RAMPART-184:
--------------------------------------------------
Assignee: Nandana Mihindukulasooriya (was: Ruchith Udayanga Fernando)
> Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified
> --------------------------------------------------------------------------------------------
>
> Key: RAMPART-184
> URL: https://issues.apache.org/jira/browse/RAMPART-184
> Project: Rampart
> Issue Type: Bug
> Reporter: Keith Godwin Chapman
> Assignee: Nandana Mihindukulasooriya
>
> Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified. Axis2 client API lets you set a property (HTTPConstants.CUSTOM_PROTOCOL_HANDLER) on the messageContext to set a CustomHTTPSProtocol handler. Rampart does not copy this over to the messageContext when sending out the request to obtain a security token.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPART-184) Secure conversation does not work
over HTTPS when a CustomHTTPSProtocol handler is specified
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPART-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Godwin Chapman updated RAMPART-184:
-----------------------------------------
Description: Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified. Axis2 client API lets you set a property (HTTPConstants.CUSTOM_PROTOCOL_HANDLER) on the messageContext to set a CustomHTTPSProtocol handler. Rampart does not copy this over to the messageContext when sending out the request to obtain a security token. (was: Secure conversation does not when over HTTPS when a CustomHTTPSProtocol handler is specified. Axis2 client API lets you set a property (HTTPConstants.CUSTOM_PROTOCOL_HANDLER) on the messageContext to set a CustomHTTPSProtocol handler. Rampart does not copy this over to the messageContext when sending out the request to obtain a security token.)
Summary: Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified (was: Secure conversation does not when over HTTPS when a CustomHTTPSProtocol handler is specified)
> Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified
> --------------------------------------------------------------------------------------------
>
> Key: RAMPART-184
> URL: https://issues.apache.org/jira/browse/RAMPART-184
> Project: Rampart
> Issue Type: Bug
> Reporter: Keith Godwin Chapman
> Assignee: Ruchith Udayanga Fernando
>
> Secure conversation does not work over HTTPS when a CustomHTTPSProtocol handler is specified. Axis2 client API lets you set a property (HTTPConstants.CUSTOM_PROTOCOL_HANDLER) on the messageContext to set a CustomHTTPSProtocol handler. Rampart does not copy this over to the messageContext when sending out the request to obtain a security token.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.