Information technology tools and resources at the UW
Husky OnNet Service Feature Updates and RoadMap
The Husky OnNet team reviews pending & proposed service features and updates this list each month. See the table below for the current service items under development and consideration. If you have questions, or would like to recommend or request service features or capabilities for Husky OnNet, please contact: email@example.com.
Thank you! Jan Eveleth, Husky OnNet Owner and Tobin Wood, Husky OnNet Manager
Pending = in development or awaiting development schedule
Proposed = ideas for features not yet confirmed for development
|Service Feature||Pending /Proposed||Estimated Delivery||Estimated Cost||Comments||Updated|
|Linux client support||Pending||DELAYED.
New est: late summer/ early fall 2017
|n/a||Husky OnNet runs on the F5 APM device. The APM device currently runs on version 12.x. The vendor recommends UW upgrade to 13.1 when it is available -possibly summer 2017. 13.1 will include support for the Linux plug in client.||6/15/17|
|New WIN and MacOS client packages from UWare||Pending||late summer/ early fall 2017||n/a||The vendor advises keeping the client apps in synch with the central APM version. New version packages for the WIN and MacOS clients will be prepared and delivered when the APM is updated to 13.1.||6/15/17|
|Husky OnNet Departmental Slice Service||Pending||DELAYED
New est: Late July 2017
Original target: Spring 2017
|$560 one-time set-up fee; $52/mo recurring fee||This service will support depts/units that would like encrypted, authorized access into their specific network subnets. The Husky OnNet Slice service will use a customer-managed UWGroup to determine authorized access.||6/15/17|
|Device Authorization for use with Husky OnNet Departmental Slice||Proposed||TBD||TBD||By adding device authorization, a department may use two authentications for access to their Husky OnNet Slice service: 1) UW NetID via UW Groups and 2) device MAC.
Update 6/15/17: initial review finds that the device MAC info is not provided to the central f5 device precluding an authorization step facilitated by the central device.