Tranquil IT Forum

Good morning,

We implemented Kerberos authentication a few months ago. Everything is working on the vast majority of the network.

Only on certain PCs is it impossible to play Kerberos (for SSO).

The logon window appears with the username entered.

If we type the password we get a login/password error.

The only log I find (server/client) is this error on the target PC:

2023-11-10 10:51:09,875 [wapttasks waitress-9 7416] WARNING Incorrect function.
2023-11-10 10:51:09,875 [wapttasks waitress-9 7416] WARNING check_auth_groups: Incorrect function.

Of course, this login is functional on other PCs where WAPT is present.

In case you needed it, all posts are up to date:

Auditing scm-waptupgrade
The installed version of the WAPT agent and the version of the package are corresponding.
2023-11-10 10:49:55,486 [wapttasks WaptTaskManager 7368] INFO Running task Inform the server of the status of this machine created by SCHEDULER
2023-11-10 10:49:56,643 [wapttasks WaptTaskManager 7368] INFO update_server_status successful (data size 1319)

So, if you have any ideas?

Thanks in advance.
Good day

Are you referring to the self-service option? Or to WaptConsole?

sfonteneau wrote: ↑Nov 10, 2023 - 1:21 PM Are you referring to self-service? Or to WaptConsole?

Good morning,

This is Self service (on the user side).

Good day

Based on your tests, is this related to the logged-in user or to the workstation itself?

sfonteneau wrote: ↑Nov 13, 2023 - 2:01 PM According to your tests, is this related to the logged-in user or to the computer itself?

Good morning.

For me, it's more related to the job itself, because it's impossible to log in with another ID.
Conversely, this same ID is functional on other workstations.

Good day

Interesting; we should check if, after attempting to log in via a command prompt, the `klist` command correctly returns a ticket from the WAPT server.

Is the self-service rule package the same on this machine as on the others?

Hello,

I just found the problem:

On the new workstations, the configuration file (wapt-get.ini) was incomplete and had a "default" configuration.

I didn't know how to modify the default configuration (other than by generating a WAPT agent).
So I installed the "WAPT Configuration Policy" package and integrated my modifications into it.

I hope this helps.
Have a good day and thanks again