authenticate - Search results , p.2
Mailing lists >> pgsql-hackers >> Thread
2024-04-01 22:07:45 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authenticated correctly as opposed to some user-related auth failure. I was hoping to find
Mailing lists >> pgsql-hackers >> Thread
2024-03-11 22:51:24 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authenticated to res->authorized. Authentication is optional, but a validator *must* check that the client
Mailing lists >> pgsql-hackers >> Thread
2023-09-06 22:11:23 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authenticating" could pretty easily subsume things like the PQsslKeyPassHook if we wanted.) The PQAUTHDATA_OAUTH
Mailing lists >> pgsql-hackers >> Thread
2023-07-13 04:51:48 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authentication requirements are and get parameters. 2. When it acquires the token, the callback is used
Mailing lists >> pgsql-hackers >> Thread
2023-07-07 21:16:05 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authenticate with Client Credentials (app secret) without bringing more dependencies. In most other cases, upstream
Mailing lists >> pgsql-hackers >> Thread
2023-07-07 18:48:26 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authentication, and it looks like that's true with today's implementation, which returns pessimistically
Mailing lists >> pgsql-hackers >> Thread
2023-04-27 17:35:20 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authentication patches. This doesn't yet address the architectural feedback that was discussed previously, so if you're primarily
Mailing lists >> pgsql-hackers >> Thread
2023-02-23 23:04:22 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authentication flow. The rfc itself does leave a lot of flexibility on specific parts of the implementation
Mailing lists >> pgsql-hackers >> Thread
2023-02-20 22:35:36 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Stephen Frost)
authentication methods than having extensions and making libpq developers have to write their own custom
Mailing lists >> pgsql-hackers >> Thread
2023-01-18 01:53:56 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authentication is one side of the whole story and the other critical one is system
Mailing lists >> pgsql-hackers >> Thread
2022-12-13 05:06:20 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authentication hook is further extensibility to support more metadata. Specifically when we add support for OAUTH
Mailing lists >> pgsql-hackers >> Thread
2022-12-08 04:25:09 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authentication reply. That is definitely a required scenario for the long term and the easiest
Mailing lists >> pgsql-hackers >> Thread
2022-12-07 23:22:51 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authenticate as the Role. - Then its native PostgreSQL role based access control takes care of privileges
Mailing lists >> pgsql-hackers >> Thread
2022-12-06 00:15:06 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Andrey Chudnovsky)
authenticate with the identity providers of their choice. 3. Client Application Developers (Data Wis, integration
Mailing lists >> pgsql-hackers >> Thread
2022-11-29 21:12:21 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authenticated ID of the bearer so that the HBA can decide whether they're authorized