Delete user through CLI runtime error about vikunja

[RoboMagus]

I see there was a problem on my part. A typo in the allowed authentication redirect url...

This should already be the case, but sometimes the names are not exposed correctly. I'm sure it works with gitlab as that's what I tested it with but I'm not sure about other providers. The usernames have to be unique across all providers so if you already have a user from another source with the same username it will fallback to generating a random one.

And that would clarify why I'm getting randomized usernames when trying to login using Authentik; I'm using the same prefered username as what I already have configured in Vikunja's local users. Oops 🥲

I'll use your suggestion to migrate my data from one account to the other. Thanks!

[kolaente]

What version are you using? Can you reproduce this with the latest unstable?

[RoboMagus]

Wow, great response time!!
I'm currently on Vikunja api version v0.18.1. Not sure how to find the docker image version though.
I'll quickly try to pull unstable and get back to you after I try to reproduce it.

[RoboMagus]

Yes, on the unstable version, I can now delete these users from commandline.
However, when trying to login now using Authentik, as I used to before, I now get an error page:

Redirect URI Error
The request fails due to a missing, invalid, or mismatching redirection URI (redirect_uri).

Related to this: Can vikunja be made to grab e.g. the preferred_username, name, nickname, or anything similar from the open-id scopes instead of creating a random username?
And would it be possible to migrate all data from an existing local user to a user created by logging in using openid?

[kolaente]

However, when trying to login now using Authentik, as I used to before, I now get an error page:

Did you upgrade to the unstable frontend as well?

Related to this: Can vikunja be made to grab e.g. the preferred_username, name, nickname, or anything similar from the open-id scopes instead of creating a random username?

This should already be the case, but sometimes the names are not exposed correctly. I'm sure it works with gitlab as that's what I tested it with but I'm not sure about other providers. The usernames have to be unique across all providers so if you already have a user from another source with the same username it will fallback to generating a random one.

And would it be possible to migrate all data from an existing local user to a user created by logging in using openid?

You could, but there's no real supported migration path or similar. You would need to manually delete the local user in the DB (not with the cli command because that would remove all user data as well) and then change the id of the other user to the one of the deleted local user. Make a backup before trying this.