Client Authentication Fail (HTTP 401) during registration to RMT-Server

[rafaprata]

I am encountering the following scenario:

• RMT-Server v2.14 (I also tested with versions 2.15 and 2.17) using helm-chart
• Kubernetes v1.24.10
• Clients running SLES 15 SP5 and 15 SP3

The server has already mirrored the necessary repositories for both clients, and when registering the clients on the RMT-Server, I observe two different outcomes:

1. SLES 15 SP3 - This is the easier scenario, as running the client setup works correctly. The repositories point to the RMT server, and I can perform the necessary upgrades on the client.
2. SLES 15 SP5 - This scenario is peculiar. Given the same context, the only significant difference is the client's operating system. It returns an authentication error when running the command /usr/bin/zypper --non-interactive refs SUSE_Linux_Enterprise_Server_x86_64, with the RMT server returning a 401 error, causing the registration to fail.

I have reviewed the logs and everything possible to understand this issue, even contacting SUSE support for assistance. However, I have not been able to resolve it. I noticed that during the SUSEConnect --write-config --url <RMT-SERVER-URL> command, it modifies repositories, services, and connections to the RMT-Server. At some point in this process, it executes a refresh services command (zypper refs), passing the services individually. This command makes an HTTP request to the RMT server. In both scenarios, the first request returns a 401 error, but in scenario 1, the second request succeeds (200), while in scenario 2, it returns 401.

I do not understand why the password generated when the system in scenario 2 was registered on the RMT server does not work for this connection. I observe that the command correctly registers the information in the /etc/zypp/credentials.d directory, and this information can be verified both in this directory and in the RMT server database.

Thank you. Rafael Souza