Page 1 of 1

Wapt self-service and password

Published: June 22, 2021 - 3:53 PM
by corriou
Hello,

I've been using Wapt for a few years now, using the Community version (currently 1.8.2.7334, on a Debian server), and I deploy packages from the console. Therefore, I rarely have the opportunity to use the self-service feature.
While trying to demonstrate it to a colleague, I encountered a problem, perhaps a bug:
my colleague uses a password ending with the two characters "£" and has an administrator account. I created a group called waptselfservice for him and added him to it. When I try to authenticate with his password, I get the message "Incorrect username or password". After changing the last character of his password (from "£" to "$"), I was able to authenticate and use WaptSelfService.
I must admit I haven't had time to investigate further yet, but I'd be curious to know the source of the problem.

Best regards,

Re: Wapt self-service and password

Published: June 23, 2021 - 12:35
by dcardon
Hello Corriou,
there was an encoding issue with the self-service login, but I believe it was fixed some time ago. Could you please try upgrading to the latest version, 1.8.2?
Regards,
Denis

Re: Wapt self-service and password

Published: June 23, 2021 - 5:24 PM
by corriou
I am currently on version 1.8.2.7334 which is the latest (currently) offered on Debian 10.

Code: Select all

Version WAPT Server : 1.8.2
Version WAPT Agent : 1.8.2.7334
version WAPT Setup : 1.8.2.7334
Version WAPT Deploy : 1.8.2.7334
Statut de la base : OK (1.8.2.1)
The machine is up to date.

Re: Wapt self-service and password

Published: July 7, 2021 - 5:24 PM
by dcardon
Hi Corriou,

there are more up-to-date versions in the community nightly build, but since not many people in the community are testing them, they've never been released (unlike the enterprise 1.8.2 versions)...

You can test a recent nightly community build to see if the bug is still present.

In any case, with the upcoming release of Discovery 2.0, Tranquil IT will let the community take charge of the development of the 1.8.2 community version, so if you want to look into it, fork the project on GitHub and start hacking the code, it could be a good opportunity. :-)

Best regards,

Denis