Tranquil IT Forum

Hello everyone,

Following the WAPT update to version 1.8, I am unable to use the SelfService feature.
Here is the error message at startup:

Unable to create file
"C:\Users\'username'\AppData\Local\waptself\waptself.ini"

Hello TomTom,

TomTom wrote: ↑January 22, 2020 - 10:25 AM Following the WAPT update to version 1.8, it's impossible to use SelfService.
Here's the error at startup:

Unable to create file
"C:\Users\'username'\AppData\Local\waptself\waptself.ini"

This is the same directory that was used by the self-service function in version 1.7.4. Could you please verify that the directory exists and if you are able to edit the file in question using Notepad? The file may be locked by another instance of the waptself.exe file.

Sincerely,

Denis

I just tested it.
The directory does exist and I can edit the "waptself.ini" file with Notepad++.

I'm answering myself:
The problem only occurs on the WAPT administration workstation...
I'm experimenting a bit and will come back to update my investigation information.

Hello everyone,

Having a bit more time to delve into WAPT SelfService, I've run into an authentication problem.

I've successfully created a SelfService package and added my group based on an existing OU in my Active Directory. I
've deployed this package to my test machine, but when I try to log in to SelfService, I consistently get the error: "Incorrect username or password."

I simply can't get it to work, no matter what I try...

If anyone happens to be able to help...

Thanks in advance,
Thomas.

Can you try the following in Python:
Or Obviously replace the username, domainname, and password

Hello TomTom,

there have been several fixes in the latest version. Are you able to reproduce the problem with version 1.8.1?

Regards,

Denis

Hello,
I'm writing to comment on this post.
I have the same problem:
when I try to open the service, I get the error message mentioned above.
I'm on version 1.8.1,
and waptself.ini is created and editable.

I have the impression that the problem is intermittent, because it worked last week with the same account on the same computer.
Since then, nothing has changed (no change of AD password or anything else...).

However, I have the impression that the problem lies with AD's password recognition... because after several attempts, it seems to lock the account.
But... I'm absolutely certain of my password...

If you have any ideas, I'd appreciate it.

Thank you

You can try switching to the following authentication method: waptserver-ldap:

https://www.wapt.fr/fr/doc/wapt-usage/w ... elfservice