Cannot update OAuth client id #1487

New Issue

vsviridov · 2023-04-08T03:23:43Z

vsviridov commented

2023-04-08 03:23:43 +00:00

Description

Hello, I've encountered a really weird bug. I've provisioned a new clientId/clientSecret pair for my Vikunja instance in my IDP software (Zitadel).

I then went to edit the config file, have updated the settings there and restarted the server.

However it still uses the old clientId.

Apparently it's cached in redis, and I had to run del openid_providers manually to get it to read the correct setting.

Vikunja Frontend Version

v0.20.5

Vikunja API Version

v0.20.4

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Hello, I've encountered a really weird bug. I've provisioned a new `clientId`/`clientSecret` pair for my Vikunja instance in my IDP software (Zitadel). I then went to edit the config file, have updated the settings there and restarted the server. However it still uses the old `clientId`. Apparently it's cached in redis, and I had to run `del openid_providers` manually to get it to read the correct setting. ### Vikunja Frontend Version v0.20.5 ### Vikunja API Version v0.20.4 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

vsviridov added the

kind/bug

label 2023-04-08 03:23:43 +00:00

konrad referenced this issue from a commit

2023-04-10 11:32:22 +00:00

fix: remove old saved openid provider settings from cache when starting Vikunja

konrad closed this issue

2023-04-10 11:32:22 +00:00

konrad commented

2023-04-10 11:32:42 +00:00

Should be fixed in 9bf535d06f. Please check with the next unstable build if your problem went away.

Should be fixed in https://kolaente.dev/vikunja/api/commit/9bf535d06f5b9bb455979b0bf3b6f0942daa1c9e. Please check with the next unstable build if your problem went away.

Sign in to join this conversation.