[
https://issues.apache.org/jira/browse/JAMES-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761759#comment-16761759
]
ASF GitHub Bot commented on JAMES-2657:
---------------------------------------
Github user randymo commented on the issue:
https://github.com/apache/james-project/pull/148
@mbaechler I can do that, What module and package should I create the
common ssl engine logic wrapping class in?
The problem is, we serve more domains than could be added to a single cert
so we have multi certs for each domain we provide mail for. We have added a
keymanager, but in order for that to work the sslEngine it is passed needs have
knowledge of where it came from otherwise we would always use the default. Hope
this clears up the problem.
> SSLEngine and SslHandler unaware of remote ip and port
> ------------------------------------------------------
>
> Key: JAMES-2657
> URL: https://issues.apache.org/jira/browse/JAMES-2657
> Project: James Server
> Issue Type: Bug
> Reporter: Randymo
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Our team uses the remote ip of the connect to determine the ssl cert we use
> for the connection. We had to make changes on our end to make that accessible
> to us at the level we needed it. It would be nice if James did this
> automatically itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
