- Joined
- Jun 18, 2018
- Messages
- 104
- Reaction score
- 4
Hi
I have noted problems, if I access the console with the MS-Edge browser (I work with Win10, 1803).
As this has cost me some hours of my life, I post it here...
Edge seems to have problems with the password fields (wrong content showed)
I had setup two SBC's and thereby had to enter the password to the tunnel.
The password is showed under settings - security settings- 3cx tunnel.
The password is first showed with asterisks and can be showed in plain text, if the "eye symbol" ist clicked.
Unfortunately - with Edge - the wrong contend ist showed - in my case the password for the console access (instead the PW for the tunnel).
With google chrome, the value is showed correct...
This has cost me hours, as the SBC's don't have worked with the wrong password and always the wrong pw was showed, if I had a further look to the pw in the console...
Note: I also have noted similar problems with Edge and other password fields in the 3cx console.
So for me it seems, as it is a problem with the "Asterisks" fields and/or some "autocomplete" functions (I think, this is an Edge problem and 3cx is not able to change the behavior, but I'm not sure..).
I have noted problems, if I access the console with the MS-Edge browser (I work with Win10, 1803).
As this has cost me some hours of my life, I post it here...
Edge seems to have problems with the password fields (wrong content showed)
I had setup two SBC's and thereby had to enter the password to the tunnel.
The password is showed under settings - security settings- 3cx tunnel.
The password is first showed with asterisks and can be showed in plain text, if the "eye symbol" ist clicked.
Unfortunately - with Edge - the wrong contend ist showed - in my case the password for the console access (instead the PW for the tunnel).
With google chrome, the value is showed correct...
This has cost me hours, as the SBC's don't have worked with the wrong password and always the wrong pw was showed, if I had a further look to the pw in the console...
Note: I also have noted similar problems with Edge and other password fields in the 3cx console.
So for me it seems, as it is a problem with the "Asterisks" fields and/or some "autocomplete" functions (I think, this is an Edge problem and 3cx is not able to change the behavior, but I'm not sure..).