Hi,
This is a known issue in NCM 7.2.
The ultimate resolution is upgrading to NCM 7.3 -- specifically 7.3.2 as of now.
Short-term workaround is to set the authentication to use password, fill in some value and then change back to none again.
Regards,
Jiri