Re: Proposal: Support custom authentication methods using hooks - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Proposal: Support custom authentication methods using hooks
Date
Msg-id CAJ7c6TNAD0XfQwoYdPDNhy=40X1w0VXVCSyb6LJSD13OXUhJkg@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Support custom authentication methods using hooks  (samay sharma <smilingsamay@gmail.com>)
Responses Re: Proposal: Support custom authentication methods using hooks  (Andrew Dunstan <andrew@dunslane.net>)
Re: Proposal: Support custom authentication methods using hooks  (samay sharma <smilingsamay@gmail.com>)
List pgsql-hackers
Hi Samay,

> I wanted to submit a patch to expose 2 new hooks (one for the authentication check and another one for error
reporting)in auth.c. These will allow users to implement their own authentication methods for Postgres or add custom
logicaround authentication. 

I like the idea - PostgreSQL is all about extendability. Also, well
done with TAP tests and an example extension. This being said, I
didn't look at the code yet, but cfbot seems to be happy with it:
http://cfbot.cputube.org/

> One constraint in the current implementation is that we allow only one authentication provider to be loaded at a
time.In the future, we can add more functionality to maintain an array of hooks and call the appropriate one based on
theprovider name in the pg_hba line. 

This sounds like a pretty severe and unnecessary limitation to me. Do
you think it would be difficult to bypass it in the first
implementation?

--
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: PATCH: add "--config-file=" option to pg_rewind
Next
From: Peter Eisentraut
Date:
Subject: Re: Design of pg_stat_subscription_workers vs pgstats