Wired Intelligent Edge

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?

Hey,

We're trying to get NetEdit up and going, but there are a couple of things that are bugging me.  

1. Authentication
   How can a product that's release version 2.0 exist without at least some sort of RADIUS/TACACS+/LDAP authentication method?  I'd venture a guess that every company implementing NE as a solution have systems in for auth, and having to create and manage users, or worse - sharing admin user access is not going to work for very long.

2. User timeout
  Why can't I set the timeout length in the GUI and have that stay put when I do an update?  A 20 minute timeout for user auth is way too short for me, especially while I'm working to get things configured while I also go about the daily tasks of supporting our users.  I log in to this thing dozens of times per day because I get interrupted and have to work on other things.

3. UI consistency
  There's an Action menu throughout.  Sometimes, there are actions that can be performed, and sometimes it's just a worthless button on the page.

Firmware repository:

Diagnostics:

Plans:

Devices:

Seems like where there aren't any useful buttons, you could  move to just include the buttons that you can push as an item instead of submenu.

4. Licensing
  Seems like it's difficult to find where to put the license in.  We purchased ~35 device licenses, but I didn't get them emailed to me, and I don't know where to add them if I do get them.

That #1 is a pretty big deal, and because of that, #2 becomes a huge annoyance (though I've updated server.servlet.session.timeout and netedit.user.session.max-age to see if that helps).  Do we have a timeline on getting some real user auth going?