Bug in Omada Controller 3.0.2

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Bug in Omada Controller 3.0.2

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Bug in Omada Controller 3.0.2
Bug in Omada Controller 3.0.2
2018-09-11 13:18:32 - last edited 2021-03-30 03:52:19

There is a bug in Omada Controller 3.0.2: it does not allow device passwords which contains non-alphanumeric characters as seen in the screenshot below.

 

You might now ask what's the problem if certain characters are not allowed in passwords?

 

The problem is that previous versions of Omada Controller up to v2.7.0 did allow such characters in passwords and if you copy your existing database from v2.7.0 to v3.0.2, the passwords are silently imported into the v3.0.2 database. Result is that one can't change device passwords anymore if an old password from v2.7.0 contains special characters.

 

Note that the password in the screenshot below is the current password - you can't correct it since it must match with the password in the database to do so.

 

BTW: as a general rule, passwords should not have a restriction to alphanumeric characters.

 

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0      
  0      
#1
Options
1 Accepted Solution
Re:Bug in Omada Controller 3.0.2-Solution
2018-09-13 01:19:01 - last edited 2018-09-13 01:28:53

Hi R1D2,

 

Thanks for your feedback. We've confirmed this bug, and it'll be fixed in the next version.

Recommended Solution
  3  
  3  
#2
Options
4 Reply
Re:Bug in Omada Controller 3.0.2-Solution
2018-09-13 01:19:01 - last edited 2018-09-13 01:28:53

Hi R1D2,

 

Thanks for your feedback. We've confirmed this bug, and it'll be fixed in the next version.

Recommended Solution
  3  
  3  
#2
Options
Re: Bug in Omada Controller 3.0.2
2018-09-13 01:28:34

Hello Lucien,

 

great, thank you!

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#3
Options
Re:Re:Bug in Omada Controller 3.0.2
2019-04-03 00:02:13
Omada 3.1.4 still does not allow special characters in the password field such as !, which is often a requirement. The password strength indicator even shows as green with the inclusion of a special character and drops to yellow without it, but they cannot be used.
  0  
  0  
#4
Options
Re: Bug in Omada Controller 3.0.2
2019-04-07 08:41:35 - last edited 2019-04-07 08:43:03

In my opinion it is a big problem that Omada Controller tries to do standard services such as HTTP services, mongodb services, jsvc privsep etc. for itself. In Linux, there are already well-working services for those standard tasks. Using existing Linux services rather than re-inventing the wheel in Omada Controller would allow to use client certificates for authentication and/or safe passwords and it also would allow to use proxy web servers. Same is true for mongodb and the dependency for jsvc (instead of for other standard privsep support such as in start-stop-daemon or daemonize) makes porting/using Omada Controller on enterprise-class servers even more complicated.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 4421

Replies: 4

Related Articles