You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2009/07/20 14:29:14 UTC
[jira] Created: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Implement Support for Multiple SSL Configurations
-------------------------------------------------
Key: SYNAPSE-563
URL: https://issues.apache.org/jira/browse/SYNAPSE-563
Project: Synapse
Issue Type: Improvement
Components: Core, Endpoints, Transports
Environment: Any
Reporter: Hiranya Jayathilaka
Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated SYNAPSE-563:
----------------------------------------
Attachment: SYNAPSE-563-update1.patch
This patch implements the required feature using a single IOReactor instance. This implementation uses a custom IOEventDispatch to control how SSL sessions are created. It doesn't enable the user to state SSL requirements at endpoint configuration level. Such requirements should also be mentioned in the axis2.xml under transport sender configuration.
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Attachments: SYNAPSE-563-update1.patch, SYNAPSE-563.patch
>
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka resolved SYNAPSE-563.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Fixed on the trunk and 1.3 branch. Thanks everyone for healthy feedback on the mailing list. Special thanks to Oleg for helping me out with httpcore APIs.
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Assignee: Hiranya Jayathilaka
> Fix For: 1.3
>
> Attachments: SYNAPSE-563-update1.patch, SYNAPSE-563.patch
>
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737469#action_12737469 ]
Hiranya Jayathilaka commented on SYNAPSE-563:
---------------------------------------------
I have committed the second patch with some minor modifications. Based on the comments by Oleg on the mailing list it appears that this is the best and easiest way to implement this feature. I'll mark this issue as resolved. If there are any concerns feel free to reopen the issue.
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Attachments: SYNAPSE-563-update1.patch, SYNAPSE-563.patch
>
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated SYNAPSE-563:
----------------------------------------
Attachment: SYNAPSE-563.patch
Attaches is a possible implementation based on a concept of SSL profiles. This enables specifying SSL requirements at endpoint level but has the drawback of using multiple IO reactors at transport level. Feedback is welcome.
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Attachments: SYNAPSE-563.patch
>
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka reassigned SYNAPSE-563:
-------------------------------------------
Assignee: Hiranya Jayathilaka
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Assignee: Hiranya Jayathilaka
> Attachments: SYNAPSE-563-update1.patch, SYNAPSE-563.patch
>
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733977#action_12733977 ]
Hiranya Jayathilaka commented on SYNAPSE-563:
---------------------------------------------
This issue is further being discussed on dev@synapse.apache.org. See http://www.nabble.com/Supporting-Multiple-SSL-Configurations-at-Sender-to24569217.html for the mail archive.
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-563) Implement Support for Multiple SSL
Configurations
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733207#action_12733207 ]
Hiranya Jayathilaka commented on SYNAPSE-563:
---------------------------------------------
Have a look at http://wso2.org/forum/thread/3928 for a somewhat related discussion
> Implement Support for Multiple SSL Configurations
> -------------------------------------------------
>
> Key: SYNAPSE-563
> URL: https://issues.apache.org/jira/browse/SYNAPSE-563
> Project: Synapse
> Issue Type: Improvement
> Components: Core, Endpoints, Transports
> Environment: Any
> Reporter: Hiranya Jayathilaka
>
> Currently Synapse can have only one SSL configuration in the HTTPS transport sender (defined as a parameter of the HTTPS transport sender in the axis2.xml). However there could be an instance where we want the sender to use different SSL configurations to connect to different endpoints. So we should be able to specify multiple SSL configurations at transport level and refer to such configurations at endpoint level.
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org