[SNMP4J] Problem with identical user name

[Frank Fock]

The VACM is used for the local SNMP entity
only. Thus, there cannot be engine ID clashes.

Regards,
Frank

Vivi Zhang wrote:
> Frank.
> 
> Thank you very much for quick response.
> 
> I see the usmUserTable is keyed by usmUser's SecurityName, and 
> engineId.   So the USM.addUser() api has no problem to put two users in 
> the userTable, as long as they have different engine id.
> 
> My next question is how to locate access group from vacmMib. In VacmMIB 
> class, the addGroup api associates a securityName with a groupName.
>  /    public void addGroup(int securityModel, OctetString securityName,  
> OctetString groupName, int storageType)
> /The key of the access group is (securityModel, securityName).   How to 
> avoid that the second addGroup call override the entry created by the 
> first addGroup call in the case I gave in my previous email:  two 
> notification targets share same V3 username?
> 
> Thanks again.
> 
> Vivi
> 
> Frank Fock wrote:
>> Hi Vivi,
>>
>> Yes, with SNMP4J you can use the same
>> security/user name for different SNMPv3 entities
>> (with different passphrases). In that case,
>> you need to use localized keys instead of
>> (clear text) passphrases.
>>
>> Best regards,
>> Frank
>>
>> Vivi Zhang wrote:
>>> Hi,
>>>
>>> I am working on an SNMP agent application using SNMP4J.
>>>
>>> I would like to support multiple V3 notification recipients, 
>>> potentially, with identical user name.
>>>
>>> Here is an example of a special case,  I have two notification 
>>> recipients:
>>> V3 notification recipient
>>>   Ip : 192.168.33.33 / 162
>>>   engineId :    engineId33
>>>   username :  bob
>>>   Auth Protocol : MD5
>>>   AuthPass :        MD5Pass
>>>   Priv Protocol :  AES
>>>   PrivPass:          AESPass
>>>
>>> V3 notification recipient
>>>   Ip : 192.168.33.34 / 162
>>>   engineId :    engineId34
>>>   username :  bob
>>>   Auth Protocol : MD5
>>>   AuthPass :        MD5Pass
>>>   Priv Protocol :  DES
>>>   PrivPass:          DESPass
>>>
>>> Here since the privacy credential is different, I can not reuse same 
>>> UsmUser objects.
>>> I wonder if the SNMP4J support this kind of use case.
>>>
>>> Thanks.
>>>
>>> Vivi
>>> _______________________________________________
>>> SNMP4J mailing list
>>> SNMP4J at agentpp.org
>>> http://lists.agentpp.org/mailman/listinfo/snmp4j
>>
> 

-- 
AGENT++
http://www.agentpp.com
http://www.snmp4j.com
http://www.mibexplorer.com
http://www.mibdesigner.com