Hello,
We have the Enterprise version 2.6.1.17472 installed on a Debian server.
When I open my WAPT console and create a new user, I am unable to change their password because the option is grayed out.
Can you help me resolve this issue?
Thank you in advance for your help,
Sincerely,
Céline
Unable to change user password
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Céline,
in CSPN mode, Kerberos authentication is required, so no local passwords are allowed (except for the admin account, which is necessary to prepare the server). If the user is a member of the group defined in wapt_admin_group, they should be able to connect to the console using Kerberos authentication.
Regards,
Denis
in CSPN mode, Kerberos authentication is required, so no local passwords are allowed (except for the admin account, which is necessary to prepare the server). If the user is a member of the group defined in wapt_admin_group, they should be able to connect to the console using Kerberos authentication.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi again Céline,
upon closer inspection, if the person is using Kerberos and there's a line corresponding to their samAccountName in the ACLs, it should allow for transparent authentication.
Best regards,
Denis
upon closer inspection, if the person is using Kerberos and there's a line corresponding to their samAccountName in the ACLs, it should allow for transparent authentication.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
I haven't enabled Kerberos for users, not intentionally anyway.
How can I check this and disable it if necessary?
Can CSPN mode be disabled?
I have another, newer WAPT server on a different domain where I don't have this problem.
Sincerely,
Céline
How can I check this and disable it if necessary?
Can CSPN mode be disabled?
I have another, newer WAPT server on a different domain where I don't have this problem.
Sincerely,
Céline
Hello,
From what I can see in my configuration files, CSPN and Kerberos are not enabled.
Is it normal that the "htpasswd" file doesn't contain the users created in the wapt console? Are these old accounts that no longer exist, or has it not been updated? I don't know if this could be related to the grayed-out "change user passwords" option from the console.
Is there an option to add to the waptserver.ini file to allow changing user passwords from the console?
Thank you in advance for your help,
Sincerely,
Céline
From what I can see in my configuration files, CSPN and Kerberos are not enabled.
Is it normal that the "htpasswd" file doesn't contain the users created in the wapt console? Are these old accounts that no longer exist, or has it not been updated? I don't know if this could be related to the grayed-out "change user passwords" option from the console.
Is there an option to add to the waptserver.ini file to allow changing user passwords from the console?
Thank you in advance for your help,
Sincerely,
Céline
