[jboss-jira] [JBoss JIRA] (LOGMGR-151) SyslogHandler should allow to set custom SSLSocketFactory

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/LOGMGR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393133#comment-13393133 ] 

James Perkins commented on LOGMGR-151:
--------------------------------------

As a temporary workaround you could extend the {{org.jboss.logmanager.handlers.TcpOutputStream}} and pass it a {{javax.net.SocketFactory}}. There is a protected constructor that accepts one. Keep in mind that the core management audit logging handles reconnecting on it's own. If you extend the {{TcpOutputStream}} and pass in a {{SocketFactory}} then the handler itself will attempt to reconnect on failed writes.


> SyslogHandler should allow to set custom SSLSocketFactory
> ---------------------------------------------------------
>
>                 Key: LOGMGR-151
>                 URL: https://issues.jboss.org/browse/LOGMGR-151
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>    Affects Versions: 2.0.5.Final
>            Reporter: Jan Kalina
>
> As part of Wildfly Elytron integration would be useful to allow to put custom *SSLSocketFactory* into *SyslogHandler*.
> It would allow to use *ssl-context* defined in elytron (with custom configuration of CAs, truststore, keystore) for syslog over TLS.
> (SyslogHandler is used for syslog audit logging in Elytron too - and currently no way to put elytron ssl-context into)



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)