[
https://issues.apache.org/jira/browse/RAMPART-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Vladov updated RAMPART-234:
----------------------------------
Attachment: rampart-https.patch
Here's the patch
Additionally it suggests that when verifying the https transport is used the
incoming transport address is used instead of the incoming transport name.
Essentially one could easily name an http transport listener in the axis
configuration "https" which will lead to a confusion in rampart and axis2. On
the other hand it will be quite convenient to be able to register several https
transport listeners, with different names, for example (using different
connector setting).
Regards,
Stefan
> Allow custom https listeners to populate the client certificate chain in the
> message context
> --------------------------------------------------------------------------------------------
>
> Key: RAMPART-234
> URL: https://issues.apache.org/jira/browse/RAMPART-234
> Project: Rampart
> Issue Type: Sub-task
> Components: rampart-core
> Affects Versions: 1.4
> Reporter: Stefan Vladov
> Assignee: Ruchith Udayanga Fernando
> Priority: Minor
> Attachments: rampart-https.patch
>
>
> Https transport listeners should be allowed to provide access to the client
> certificate chain (eg. Axis2 NIO SSL transport listener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
