Re: [OAuth2] Infrastructure for tracking token expiry time

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: VASUKI M <vasukianand0119(at)gmail(dot)com>
Cc: Ajit Awekar <ajitpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [OAuth2] Infrastructure for tracking token expiry time
Date: 2026-02-16 19:40:09
Message-ID: CAN4CZFOe-0jTR7_s2uciX9TNKxRvd2h8avAw9iFO6VPu0CChsQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

This API looks simple for providers that use JWT access tokens, but
what about providers that use opaque tokens and an introspection API
to check validity instead? Some validators might not be able to
provide anything meaningful without a periodic call to a "check
validity now" method, and even some providers that use JWT access
tokens support immediate revocation, where these periodic checks would
be useful.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-02-16 19:47:07 Re: generating function default settings from pg_proc.dat
Previous Message Jeff Davis 2026-02-16 19:36:36 Re: Expanding HOT updates for expression and partial indexes