Marc 'risson' Schmitt

` --data password=user-pw \` this should be an app password instead of the user's password (see https://github.com/goauthentik/authentik/issues/5860#issuecomment-1577081591)

Yeah those configuration options have been an issue. I'd rather we remove use_pgbouncer and use_pgpool entirely, and directly expose the django options conn_max_age and disable_server_side_cursors, with pointers in the documentation...

> Happy to work on a follow-up commit to also expose `disable_server_side_cursors` and deprecate `use_pgbouncer` (+ doc updates). Unfortunately, I am not familiar with pgpool to also contribute changes for...

> My latest commit goes ahead with deprecating USE_ settings as it was my original understanding Yeah I think that's the best route. I was just saying that in theory...

/cherry-pick version-2024.12

Just tried this with the authorization flow set to `default-provider-authorization-implicit-consent` on an oauth provider, and the `offline_access` scope selected, I don't get prompted for consent when logging into the app....

We probably won't be implementing this anytime soon, as the performance would be appalling

> Why would the performance be appalling? The LDAP outpost is already doing this mapping; it's just currently using a hardcoded mapping instead of a user-controlled mapping. That's exactly why...

I'm pretty sure dokuwiki isn't the only one that requires this. From my discussions with other users, Grafana and ArgoCD (and probably others) are also candidates for this change. @BeryJu...

> psycopg.errors.DataCorrupted: could not read block 1 in file "base/16384/16403": read only 0 of 8192 bytes Looks like your database is corrupted. I'd recommend restoring from a backup.