Bug 53995 – "Authentication error" pop up

Bug 53995 - "Authentication error" pop up


Summary:	"Authentication error" pop up

Status:	NEW

Product:	UCS@school
Classification:	Unclassified
Component:	Veyon
Version:	UCS@school 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-10-29 13:28 CEST by Jürn Brodersen
Modified:	2023-02-06 16:11 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.257
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:	Yes
Flags outvoted (downgraded) after PO Review:
Ticket number:	2022121221000259
Bug group (optional):	Troubleshooting
Max CVSS v3 score:

Attachments
Check port (1.65 KB, patch) 2023-01-30 18:50 CET, Jürn Brodersen	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jürn Brodersen

2021-10-29 13:28:49 CEST

"Authentication error" pop up

Upon start or restarting the windows veyon service an "Authentication error" pop up is shown (on windows).

The reason for this pop up is the GET /authentication/ command which we use as a ping.

The pop up is only shown once for a host but "Authentication failed for ..." is logged every second for each ping command in the veyon log on windows.

How to reproduce:
- Open the computerroom with a windows client
- Restart the veyon service on the windows client
- The message should now pop up

Relevant files:
veyon: server/src/ComputerControlServer.cpp (For the error message)
ucs@school: ucs-school-veyon-client/veyon_client/client.py (ping command)

Comment 1 Mirac Erdemiroglu

2023-01-13 08:50:12 CET

Another customer effected Ticket 2022121221000259

Comment 3 Jürn Brodersen

2023-01-30 18:50:40 CET

Created attachment 11025 [details]
Check port

The upstream developer suggested checking the port directly instead. For an example see the attached patch. But at least in my test, even just opening the port already resulted in an error on the windows machine. Due to time constrains I didn't investigate that any further.

Maybe port 11400 (also used by veyon) can be used or I just did something wrong?

Note:
We do not use an authenticated call because that might be cached by the veyon proxy.