james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-2657) SSLEngine and SslHandler unaware of remote ip and port
Date Wed, 06 Feb 2019 14:06:00 GMT

    [ 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:

    @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

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message