Every Syscob user must have "Full" control of their HKEY_CURRENT_USER hive of their Registry. As this is an inherent right of all normal Windows® users, excepting certain limited accounts like "Guest," this usually does not require any configuration. Within this hive the application only uses the "Software\Syscob" key.
The user must also have "Full" control of the "Software" key of their HKEY_LOCAL_MACHINE hive. Within this hive only the following subkeys are used by the Export-It application:
The Registry access rights listed above are sufficient for most users, but when use of Digital Certificates is required then there is one additional requirement:
The user whose logon provides Secure EDI [SEDI] communications support for all users must also have "Full" control of the "Local Machine Certificate Store" when SEDI exchanges with the Australian Customs Service "Integrated Cargo System" [ICS] are used. This “protected” part of the Registry is where Digital Certificates used for Customs SEDI are stored. Assuring access to the Digital Certificates, and their private keys, may be difficult on Windows® Vista “home” editions (including Ultimate) or may be inadvisable on Windows® “server” editions (due to security policies) and Syscob recommends avoiding placement of the SEDI user on hardware using such environments.
Note that for exporters who do not do direct EDI interchanges with the Customs ICS, meaning that SEDI does not need to employ Digital Certificates, the additional requirement above does not apply.
