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: help@uw.edu.
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/Delivered | Estimated Delivery | Estimated Cost | Comments | Updated |
| Single SignOn with Husky OnNet | Proposed Feb. 2018 | Use Windows credentials at system start up to automate the login of the HON win app – user signs into the Windows system, the system automatically starts the HON app and logs the user into the HON app.
May 2018: Initial reviews look promising; more investigation/testing required. |
5/2018 | ||
| Downloadable WIN and MacOS client apps customized with HON-D server names included | Proposed Aug 2017 | To use HON-D with WIN or MacOS devices, users download the client apps from UWare. These client apps are preconfigured with the general Husky OnNet servers. To use a HON-D server, users must ‘add a server’ and enter the department’s HON-D server name. In this feature request, the department has asked the HON team to prepare customer WIN and MacOS clients with the HON-D servers already included.
5/2018: the team has reviewed this request. This is outside the scope of the team’s resources at this time. |
5/2018 | ||
| Device Authorization for use with Husky OnNet Departmental Slice | Proposed Feb. 2017 | 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. |
6/15/17 |
