Closed locksmithone closed 9 months ago
Thanks for the heads up. We'll address this in the upcoming v1.4 release.
I double checked this with the current release going out today or tomorrow RELEASE/v1.4. The isITAR
property is not expected for the registration, but is expected for the supporting documentation uploads. This is accurate in the protocol specification.
Thank you. At least, current versions of clients need no modification then.
While submitting a new ESV to the demo server, the ITAR and alphabetSize fields were removed from registration files. But while attempting to register, here is a portion of the error returned by the server:
It would seem the ESV server still expects ITAR values.