On Mon, Aug 1, 2016 at 5:21 PM, Jeff Janes wrote:
> On Mon, Aug 1, 2016 at 1:32 PM, John McKown
> wrote:
> > On Mon, Aug 1, 2016 at 2:49 PM, Jeff Janes wrote:
> >>
> >> On Mon, Aug 1, 2016 at 11:40 AM, Joseph Kregloh <
> jkreg...@sproutloud.com>
> >> wrote:
> >> > Hi,
> >> >
> >> > Is there a w
On Mon, Aug 1, 2016 at 1:32 PM, John McKown
wrote:
> On Mon, Aug 1, 2016 at 2:49 PM, Jeff Janes wrote:
>>
>> On Mon, Aug 1, 2016 at 11:40 AM, Joseph Kregloh
>> wrote:
>> > Hi,
>> >
>> > Is there a way to force the user being sent to LDAP?
>> >
>> > For example I have the following entry in my pg
John McKown writes:
>âPerhaps what is necessary is something akin to the UNIX "sudo" facility.
> That is, an SQL statement prefix which, if used, runs the given SQL
> statement as a PG superuser. You then GRANT(?) authority to that facility
> like you would to a table or database or ... . E.g. G
On Mon, Aug 1, 2016 at 2:49 PM, Jeff Janes wrote:
> On Mon, Aug 1, 2016 at 11:40 AM, Joseph Kregloh
> wrote:
> > Hi,
> >
> > Is there a way to force the user being sent to LDAP?
> >
> > For example I have the following entry in my pg_hba.conf file:
> > hostapdb apuser 10.0.
On Mon, Aug 1, 2016 at 11:40 AM, Joseph Kregloh wrote:
> Hi,
>
> Is there a way to force the user being sent to LDAP?
>
> For example I have the following entry in my pg_hba.conf file:
> hostapdb apuser 10.0.20.1/22 ldap
> ldapserver="389-ds1.sl.com:389" ldapbasedn=