Windows somehow aggregates the permissions allowed for all the Server
Principals (logins) associated with global groups of which your account is
a member. It’s a disaster. We would shortcut that disaster by making a
single group a PostgreSQL login.
It would be bad, but not as awful as SQL Server.
On 2024-07-10 07:27:29 -0700, Ian Harding wrote:
>
>
> On Wed, Jul 10, 2024 at 7:10 AM Peter J. Holzer wrote:
>
> On 2024-07-09 03:35:33 +, Buoro, John wrote:
> > I've dusted off my C books and coded a solution.
> [...]
> > When using SSPI you can grant access to a user by g
On Wed, Jul 10, 2024 at 7:10 AM Peter J. Holzer wrote:
> On 2024-07-09 03:35:33 +, Buoro, John wrote:
> > I've dusted off my C books and coded a solution.
> [...]
> > When using SSPI you can grant access to a user by giving the login name
> as
> > firstname.lastname@SOMEDOMAIN for example.
>
On 2024-07-09 03:35:33 +, Buoro, John wrote:
> I've dusted off my C books and coded a solution.
[...]
> When using SSPI you can grant access to a user by giving the login name as
> firstname.lastname@SOMEDOMAIN for example.
> PostgresSQL has no concept of groups, just roles.
> The code provided
On 2024-04-19 11:53, Buoro, John wrote:
SSPI Kerberos\NTLM authentication (Windows environment) currently only
authenticates users, however, it does not authenticate a user against
an LDAP \ Active Directory group.
Can you please look at making this possible?
Sounds like it'd be pretty usef
Hi,
SSPI Kerberos\NTLM authentication (Windows environment) currently only
authenticates users, however, it does not authenticate a user against an LDAP \
Active Directory group.
This makes administration complex because an administrator would need to
add\remove each user to\from an instance or
