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 15:43:00 GMT

    [ https://issues.apache.org/jira/browse/JAMES-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761871#comment-16761871
] 

ASF GitHub Bot commented on JAMES-2657:
---------------------------------------

Github user randymo commented on the issue:

    https://github.com/apache/james-project/pull/148
  
    will do, and yes we have between 7-10 different domains handled by a single(technically
2, 1 for starttls and 1 for always ssl) instance of james depending on the geolocation of
the data center it is in. Each geolocation also has a different map of ip to cert because
of this.


> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message