# OIDC in PostgreSQL: With Keycloak | Percona Community

**URL:** <https://forums.percona.com/t/oidc-in-postgresql-with-keycloak-percona-community/40066>\
**Category:** Community website\
**Created:** [January 19, 2026, 2:56pm UTC](https://forums.percona.com/t/oidc-in-postgresql-with-keycloak-percona-community/40066 "2026-01-19T14:56:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [January 19, 2026, 2:56pm UTC](https://forums.percona.com/t/oidc-in-postgresql-with-keycloak-percona-community/40066/1 "2026-01-19T14:56:25Z")

</div>

We spent a long time, [two](https://percona.community/blog/2025/10/28/oauth-oidc-validators/) blog [posts](https://percona.community/blog/2025/11/17/oidc-in-postgresql/) to be specific, talking about OAuth/OIDC in theory. Now we’ll take a more practical look at the topic: how can we configure PostgreSQL with a popular open source identity provider, [Keycloak](https://www.keycloak.org/), and our [pg\_oidc\_validator](https://github.com/percona/pg_oidc_validator) plugin?

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/01/19/oidc-in-postgresql-with-keycloak](https://percona.community/blog/2026/01/19/oidc-in-postgresql-with-keycloak)