Post-installation method, no login to Cockpit possible (Wrong user name or password)

[HachimanSec]

Hello,

I hope I didn't miss any thread, but I searched the forums and didn't find anything.

I am trying to setup a test deployment of T-pot. The installation succeeds, however I am unable to login to the cockpit. Installation was done via post install method.

There is always the error of Wrong user name or password for the Cockpit website login.

However, the OS username and password combi is correct and still works via SSH login.
Login to <IP>: 64297 works, via username and password I created during installation.

I explicitly read First start and user types.

Anyone any ideas?

Thanks!

Below are my debug informations:

T-pot version: T-Pot 22.04.0, latest via git as of 2022-04-26
T-pot edition: Standard
Architecture: Cloud
Hoster: DigitalOcean
OS: Debian 11 x64
CPU: 4 vCPUs
RAM: 8GB / 160GB Disk
Install errors: None
df -h:

Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           796M  3.8M  792M   1% /run
/dev/vda1       160G   12G  142G   8% /

lsb_release -a && uname -a

No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)

Release:	11
Codename:	bullseye
Linux certainaugust 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux

systemctl status tpot:

Loaded: loaded (/etc/systemd/system/tpot.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-04-26 15:28:40 UTC; 4min 11s ago

[HachimanSec]

I actually found another thread: #945

The cockpit apparently requires tsec as <os_username> (to stick with the nomenclature of first start. Other OS usernames are not accepted.)

SSH'ing into the server and adding a new user named tsec solves the problem.
adduser tsec

Either the documentation, the installer or the Cockpit access config could be updated to address this behaviour.

EDIT: The newly added tsec user can login to the Cockpit, however it is not admin. Root is admin, but I can't login. Anyone any idea how I can manually promote tsec to Cockpit admin? I cant find anything in the doc.

[HachimanSec]

PS: Interestingly the original OS account root is listed in the Cockpit Accounts menu. It simply doesnt work for the login.

As mentioned above, the problem is that the newly added user is not an admin. Root is admin, but can't login and it seems one can't make an os user a Cockpit admin via CLI.

[t3chn0m4g3]

Yes, usually a Debian Install offers to add a standard user during install and this user is then added to Cockpit. However this seems to be different in some cases. Since Cockpit is a system service it adds root for elevation.

[t3chn0m4g3]

Will look into it. Probably related to #1074.

[HachimanSec]

Danke dir @t3chn0m4g3. I just update my comments with some more info.

[t3chn0m4g3]

Welcome @HachimanSec and thanks for reporting!

[frogman1370]

I know this thread is a couple years old and I was looking into the same thing, but in reviewing the docs for 22.04:

64294 | tcp | incoming | T-Pot Management: Sensor data transmission to hive (through NGINX reverse proxy) to 127.0.0.1:64305 -- | -- | -- | --

I'm assuming that this Cockpit is only meant for a distributed model where it uses the web interface to send data? Let me know if I'm incorrect on that assumption. I created a 'tsec' user (rebooted) and still unable to access the interface.