You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/06/21 13:02:00 UTC

[jira] [Commented] (NIFI-4099) SNMP processors cannot be restarted with SNMPv3 & security

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

Joseph Witt commented on NIFI-4099:
-----------------------------------

Hello, a single PR should be quite fine.  Awesome that you're taking it on.

> SNMP processors cannot be restarted with SNMPv3 & security
> ----------------------------------------------------------
>
>                 Key: NIFI-4099
>                 URL: https://issues.apache.org/jira/browse/NIFI-4099
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.4.0
>            Reporter: Lars Francke
>              Labels: snmp
>
> The SNMP processors currently fail when stopped & started again because snmpTarget is not set to null and only if it is are the user credentials added to the current USM/Engine.
> So what happens is that SNMP4j complains that there is no username.
> I'll provide a patch that fixes this.
> In addition I'd like to update SNMP4J from the version that's being used 1.x (from 2009) to 2.5.6 from 2017. And I'd love to also do a code cleanup run. I'd prefer to have it all in one patch (it still won't be large) but if really needed I can separate it out into three patches.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)