RE: [EXT] Re: GSS Auth issue when user member of lots of AD groups - Mailing list pgsql-bugs

From Chris Gooch
Subject RE: [EXT] Re: GSS Auth issue when user member of lots of AD groups
Date
Msg-id DS0PR22MB597141E2FBF921B3B3480452BE64A@DS0PR22MB5971.namprd22.prod.outlook.com
Whole thread Raw
In response to Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Thanks again for sharing the patches Tom.

I have just tested the following combinations on v17 and all working as expected, both with tickets less thank 16k and
greaterthan 16k. 

1. Patched Client to Unpatched Server
2. Unpatched Client to Patched Server
3. Patched Client to Patched Server


Thanks,
Chris

-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Sunday, May 25, 2025 4:51 PM
To: Chris Gooch <cgooch@bamfunds.com>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>; pgsql-bugs@lists.postgresql.org
Subject: Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups

I wrote:
> Chris Gooch <cgooch@bamfunds.com> writes:
>> Are there specific test cases you would like me to try?

> Obviously, check if it works for the user with lots of AD groups.
> But beyond that, just check it in everyday use.

Oh --- one specific scenario that would be good to check is to verify that patched libpq can still use GSS with
unpatchedserver and vice versa, so long as the ticket doesn't exceed 16K. 

            regards, tom lane

This email and any attachments should not be construed as an offer or recommendation to sell or buy or a solicitation
ofan offer to sell or buy any specific security, fund or instrument or to participate in any particular investment
strategy.The information contained herein is given as of a certain date and does not purport to give information as of
anyother date. Although the information presented herein has been obtained from sources we believe to be reliable, no
representationor warranty, expressed or implied, is made as to the accuracy or completeness of that information. Past
performanceis not indicative of future results. 

CONFIDENTIALITY NOTICE: This message and any attachment are confidential. If you are not the intended recipient, please
telephoneor email the sender and delete this message and any attachment from your system. If you are not the intended
recipientyou must not copy this message or attachment or disclose the contents to any other persons. 

Balyasny Asset Management (UK) LLP is authorised and regulated by the Financial Conduct Authority in the UK. Balyasny
AssetManagement LP is registered as an Investment Advisor with the Securities and Exchange Commission in the USA. 

BAM prohibits all personnel from having any business related communications over text message or other unapproved
communicationapplications. Unless pre-approved, BAM employees are only permitted to communicate over email, Bloomberg
andBAM telephone lines. 



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18937: New error class 10 for XQuery errors lacks a "standard" error code
Next
From: Masahiko Sawada
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5