I've setup Vikunja API and Client on my server, and it's configured to use my OpenID provider, Authentik.
On previous stable versions, I was actually able to login, before performing any action would subsequently get me kicked out, and logging in again immediately wouldn't work. I could check back then that calls to the API to login would stall out for an entire minute before getting dropped. They did seem to reach the server from the Vikunja logs, but it did not appear to want to give a proper response back to the client.
I'm now on unstable for both the API and Client, and logging in from the OpenID provider gets directed to a page with just the MOTD on it. Attempting to navigate to any of the servicable parts of client would just prompt you to login again. Unfortunately checking logs for the API shows that no request was even possibly made, suggesting that the internal router may just be dropping it, or the URL doesn't exist.
For instance it is redirecting to https://sub.domain.tld/auth/openid/..., but both the the API claims it's never reached, so I assume it's something with the URL.
I've setup Vikunja API and Client on my server, and it's configured to use my OpenID provider, Authentik.
On previous stable versions, I was actually able to login, before performing any action would subsequently get me kicked out, and logging in again immediately wouldn't work. I could check back then that calls to the API to login would stall out for an entire minute before getting dropped. They did seem to reach the server from the Vikunja logs, but it did not appear to want to give a proper response back to the client.
I'm now on unstable for both the API and Client, and logging in from the OpenID provider gets directed to a page with just the MOTD on it. Attempting to navigate to any of the servicable parts of client would just prompt you to login again. Unfortunately checking logs for the API shows that no request was even possibly made, suggesting that the internal router may just be dropping it, or the URL doesn't exist.
For instance it is redirecting to `https://sub.domain.tld/auth/openid/...`, but both the the API claims it's never reached, so I assume it's something with the URL.
When you get redirected to the client where it shows just the motd, what does that look like?
Are there any errors in the browser console at that point?
Are you using openid as the only auth provider or do you have Vikunja's local auth still enabled?
When you get redirected to the client where it shows just the motd, what does that look like?
Are there any errors in the browser console at that point?
Are you using openid as the only auth provider or do you have Vikunja's local auth still enabled?
Are there any errors in the browser console at that point?
Nope. It's completely void of any errors, just warnings about fonts.
Are you using openid as the only auth provider or do you have Vikunja's local auth still enabled?
OpenID is enabled as the only auth provider, Local auth is completely disabled.
> When you get redirected to the client where it shows just the motd, what does that look like?
It's just a page with the llama in the bottom right and the MOTD in the middle. Very blank with no additional information. I can screenshot it if you really want. From what I can tell it's literally just this page: https://kolaente.dev/vikunja/frontend/src/branch/main/src/components/home/contentNoAuth.vue
> Are there any errors in the browser console at that point?
Nope. It's completely void of any errors, just warnings about fonts.
> Are you using openid as the only auth provider or do you have Vikunja's local auth still enabled?
OpenID is enabled as the only auth provider, Local auth is completely disabled.
I've setup Vikunja API and Client on my server, and it's configured to use my OpenID provider, Authentik.
On previous stable versions, I was actually able to login, before performing any action would subsequently get me kicked out, and logging in again immediately wouldn't work. I could check back then that calls to the API to login would stall out for an entire minute before getting dropped. They did seem to reach the server from the Vikunja logs, but it did not appear to want to give a proper response back to the client.
I'm now on unstable for both the API and Client, and logging in from the OpenID provider gets directed to a page with just the MOTD on it. Attempting to navigate to any of the servicable parts of client would just prompt you to login again. Unfortunately checking logs for the API shows that no request was even possibly made, suggesting that the internal router may just be dropping it, or the URL doesn't exist.
For instance it is redirecting to
https://sub.domain.tld/auth/openid/..., but both the the API claims it's never reached, so I assume it's something with the URL.When you get redirected to the client where it shows just the motd, what does that look like?
Are there any errors in the browser console at that point?
Are you using openid as the only auth provider or do you have Vikunja's local auth still enabled?
It's just a page with the llama in the bottom right and the MOTD in the middle. Very blank with no additional information. I can screenshot it if you really want. From what I can tell it's literally just this page: https://kolaente.dev/vikunja/frontend/src/branch/main/src/components/home/contentNoAuth.vue
Nope. It's completely void of any errors, just warnings about fonts.
OpenID is enabled as the only auth provider, Local auth is completely disabled.