[SNMP4J] Agent fails to send V3 "inform" notification

[Mark Gorokhov]

My TestAgent has EngineID="80:00:6c:ae:01:0a:05:00:8a"
MIB Explorer has EngineID="80:00:13:70:01:0a:05:00:8a"

I'm sending "inform" notification from my TestAgent. Debug confirms that VACM access is allowed. Then log is as follows (formatted):

==================================================
RFC3414 §3.1.4.b Outgoing message is not encrypted
Adding cache entry: StateReference[...]
Running pending sync request with handle ...
Sending message to 127.0.0.1/165 with length 61: ...
Received message from /127.0.0.1/165 with length 87: ...
SNMPv3 header decoded: ... 
Accepting zero length security name
Removed cache entry: StateReference[...]
RFC3412 §7.2.10 - Received PDU (msgID=442508714) is 
    a response or an internal class message. 
    PduHandle.transactionID = 44522832
MPv3 finished
Searching pending request with handlePduHandle[44522832]
Send new request after report.
(A-line)Context engine ID of scoped PDU is empty! 
    Setting it to authoritative engine ID: 
    80:00:13:70:01:0a:05:00:8a
(B-line)getUser(engineID=80:00:13:70:01:0a:05:00:8a, 
    securityName=abc)
(C-line)USM.getUser - User 'abc' unknown
(D-line)Security name not found for engineID=
    80:00:13:70:01:0a:05:00:8a, securityName=abc
==================================================

Investigation.

D-line: Reported engineID is MIB Explorer's engineID and not TestAgent's engineID. That's why security name is not found. MIB Explorer's engineID is not known in TestAgent for security name "abc". UsmUserTable has user "abc" with associated TestAgent's engineID. This problem is logged in B-line and C-line.

A-line: Why context engine ID of scoped PDU is empty? Is this a root of the problem?

What am I missing to setup V3 "inform" notification?

Thanks,
Mark G.