Automated Access Policy: HughesNet® Installation Portal
- Hughes must be informed of all automated systems/processes
- Point of Contacts (Email/Phone)
- Discussions with Hughes IT are encouraged
- You can use Installer Feedback (Installation Portal Issue), to initiate the discussions
- Hughes will need to know all the user accounts beginning automated
- Automated accounts must be requested separately from manual accounts, through same request mechanism
- Dealers go through their Distributors, not directly through Hughes
- Normally we add "-autoprocess" to end of account or "-auto{software name}" if multiple users are using 3rd party software
- XML access will only be given to these separate accounts
- XML WebServices must be used for ALL updates
- Only exception is Service Order Attachments, WebService to-be developed
- Do not send update posts to any other form! Example: FSO Closure, FSO View Service Order, FSO Service Order Activities, …
- There will be more notice on changes to WebServices (Possibly even supporting multiple versions for a short period of time)
- We’ll be adding more WebServices in the near future
- Read-only requests can be performed on any of the web pages.
- Example all the search pages support and XML output
- Most pages respond to both a Get and a Post
- Try to keep polling frequency more than 15 mins
- The website is constantly changing, to support business needs. Hughes will try to keep everyone informed of these changes
- Hughes doesn’t guarantee any 3rd party software will continue to work after changes.
- Session/Logins should be reused where possible, instead of login in collecting information then logging out.
- Authentication is a Heavy weight procedure
- There are protection mechanisms in place, to restrict too many logins
- Try to change the Browser Agent to indicate which Software is beginning used
Any violations of this policy may result in deactivation of Distributor/Dealer account(s)!
Any user account consuming too much system resources may also be deactivated.