Registry.py API routes do not check that request is coming from the host matching the --host test parameter

[MichalChomo]

This behaviour will cause the IS-04 test_01_01 (Node does not attempt to register with an unsuitable registry) to fail even if the host specified by --host behaves correctly, provided there is another host on the network which tries to register with the unsuitable mocked registry. This is because the mocked registry will accept registration request from any host on the network.

Is this expected/desired behaviour?

[jonathan-r-thorpe]

Yes this is expected behaviour as the mock registry will accept any and all registration requests.

The option to restrict registrations to the Node under test ip have been discussed but not implemented so far.

One work around would be to alter the priority of the mock registry or change the preferred priority of the other NMOS Nodes on the network to stop them registering with the mock.

FYI the mock registries priorities are defined in the dns_records.zone file found in test_data/IS0401 which AFAICS define priorities between 10 and 60.