First steps / discoveries

[jadudm]

For anyone poking the package...

I was unsure how to change the password for the default user. Some digging around yielded the following...

1. I had to generate a password hash. Log into the terminal for the app and run:

htpasswd -bnBC 10 "" PASSWORD | tr -d ":\n" | sed 's/$2y/$2a/' && echo

replacing the word PASSWORD with your password. I used a long combination of words and numbers with no spaces. This will output a bcrypt password hash:

$2a$10$GpIUtD/NDyfpVkQuaVfDde7M5SjcHdcmN9e49kFlgoeVsmMnrQ0wm

or similar. (Don't use that one.)

2. Log into the terminal, and open up the Postgres prompt.

update user_account set password = '$2a$10$GpIUtD/NDyfpVk...' where email = 'admin@cloudron.local';

Again, put your password hash between the single quotes.

Now, you can log in as the administrative user with the password you hashed.

3. Log in using your SSO/Cloudron user.

I think a package update might be needed. The OIDC users do not have any privileges out-of-the-box.

https://github.com/plankanban/planka/issues/661

It might be setting OIDC_IGNORE_ROLES would allow OIDC users to create boards. There might be more env vars necessary, but that one seems critical. It seems like the administrative user cannot (out-of-the-box) modify the roles for OIDC users (https://github.com/plankanban/planka/issues/1112). Again, that env var may be part of the puzzle.

In the meantime, I again opened up the Postgres prompt, and did:

SELECT * FROM user_account

I found my username (which was my expected Cloudron username, so it was easy to find/there were no surprises), and then modified that row to give myself more permissions:

UPDATE user_account SET role = 'projectOwner' WHERE username = 'MYUSERNAME';

This gave me enough permissions to do things.

My hope is that if the right env vars were set, that I would not need to grant my OIDC users permissions via the admin user.

[scooke]

None of your postgres commands worked for me. In fact, for the admin password change the first time I get a notice that ALL lines are ignored, like psql: warning: extra command-line argument "UPDATE" ignored, but when I repeat it the return is UPDATE 1. But then when logging in it tells me the details are wrong. I've restarted the app, and not. Same thing.

Even for what looks like an easy SELECT I get bash: SELECT: command not found .

Oh well, I'll delete it and come back to it in a few weeks.

[nebulon]

Indeed it looks like that admin account created from env variables as described in https://docs.planka.cloud/docs/configuration/admin-user/#by-setting-environment-variables results in the change password UI to be hidden.

Creating an admin user with the planka cli does not have that effect. Trying to get the package fixed up here

[nebulon]

A new package version is out, which enables the normal profile configuration UI parts also for the admin user