search

JoshuaJeong / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

incoming anchor enabled outgoing messages #155

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.http:// ... 8081/config-ui/config/domain?id=360448
2.anchors tab
3.add one anchor, check "Incoming" only

What is the expected output? What do you see instead?
Expected send a Direct message to fail
Was able to send, and also received the MDN.

What version of the product are you using? On what operating system?
compiled from source downloaded 2011-06-14

Please provide any additional information below.

Original issue reported on code.google.com by NFinst...@gmail.com on 12 Jul 2011 at 7:56

GoogleCodeExporter commented 8 years ago 
were you able to send a regular (non MDN) message with this configuration?  
MDNs are special cases because they implement QoS and are handled differently 
from an incoming/outgoing anchor perspective.  The .NET RI recently implemented 
something similar.

Original comment by abarea...@gmail.com on 12 Jul 2011 at 8:05

GoogleCodeExporter commented 8 years ago 
yes, send regular (non MDN), received MDN

Original comment by NFinst...@gmail.com on 12 Jul 2011 at 8:10

GoogleCodeExporter commented 8 years ago 
Looking at the code, the WS configuration uses the uniform trust anchor 
configuration by default unless the multidomain setting is applied.  The 
uniform setting applies the same anchor policy across all domains.  I'm 
debating if multidomain should be the default setting (it does work with one 
domain, bad naming convention).

Try adding the following setting in the "settings" section of the config ui and 
restart your gateway:

Name: AnchorResolverType
Value: multidomain

The multi domain anchor resolver does require that you have at least one anchor 
defined to be outgoing and one to be incoming.  You should always have the 
domain's own anchor in its anchor list, and more than likely that will be set 
as both incoming and outgoing.  I could see use cases where a HISP may not 
always want this to be the case, so I am considering logging a bug/enhancement 
to allow an empty set of incoming or outgoing anchors (but not both).  

Let me know if the configuration above works for you.

Original comment by gm2...@cerner.com on 18 Jul 2011 at 3:08

GoogleCodeExporter commented 8 years ago

Original comment by gm2...@cerner.com on 8 Sep 2011 at 7:28

GoogleCodeExporter commented 8 years ago 
The WS configuration has been updated to use the multi-domain setting by 
default regardless of the number of domains.  The uniform setting really only 
makes sense for development purposes.

Original comment by gm2...@cerner.com on 18 Oct 2011 at 5:05

GoogleCodeExporter commented 8 years ago

Original comment by gm2...@cerner.com on 20 Nov 2012 at 3:43