Hi! (Vikunja dev here) As @girish correctly pointed out, you don't need to enable openid to use the api. In fact, when you're using the Vikunja Frontend or Desktop app it already uses the api. The login endpoint is your way to go to get the api token. I hope to build "classic" api tokens in the future you may know from other websites (like github) where you can create a long-lived token in the user settings and use it without a login.

@roundhouse1924 thanks for the heads up, our release notification app was stalling for a few days. The new version is published now.

@kolaente thank you ! yep, I understand it's probably a platform default.

@kolaente it does catch the eye ! and I like the domain selection strategy

thanks, I have made a new package now.

Relevant issue in the upstream project: https://kolaente.dev/vikunja/frontend/issues/484

@scooke That sounds a lot like a bug - if it happens again, could you ping me so that I can try to reproduce it?

@kolaente Sorry, I should have been clearer that setting the time zone was what got the app running again. I don't recall clearing any cache, despite @girish's kind advice. I'll try disabling the cache, even though I can't say I've noticed any slowdowns. It either has worked well, or not worked at all! Thanks.

For future readers, adding a link to the upstream discussion here - https://community.vikunja.io/t/long-time-regular-main-user-being-asked-to-confirm-email-address/195/

@humptydumpty @scooke I have provided the upstream author backtrace at https://community.vikunja.io/t/400-bad-request-on-first-namespace-creation-error-500-on-api-v1-info/170/15

@girish Someone already asked this on there: https://community.vikunja.io/t/how-to-delete-users/17 There's no way to delete users on the frontend or through the API. It's low priority for them but it's on the roadmap. This was back in May 2020.

@cloudron_hacky good catch. I have pushed an update to the app now that fixes this.