Re: pg_hba.conf "authentication file token too long, skipping" - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_hba.conf "authentication file token too long, skipping"
Date
Msg-id 1567990.1690217495@sss.pgh.pa.us
Whole thread Raw
In response to pg_hba.conf "authentication file token too long, skipping"  ("Zechman, Derek S" <Derek.S.Zechman@snapon.com>)
Responses RE: pg_hba.conf "authentication file token too long, skipping"
List pgsql-bugs
"Zechman, Derek S" <Derek.S.Zechman@snapon.com> writes:
> hostssl all +fnc_personal_account_rl XXX.XX.X.X/16 ldap ldapserver=xxxx-xxxx-xx-xx.mydomainname.com
ldapbasedn="OU=Users,OU=Primary,OU=All,DC=mydomainname,DC=com"
ldapbinddn="CN=abc_postgres_sa,OU=T1-ServiceAccounts,OU=Tier1,OU=Admin,OU=All,DC=mydomainname,DC=com"
ldapbindpasswd="30characterpassword"
ldapsearchfilter="(&(objectClass=user)(sAMAccountName=$username)(|(memberof=CN=xxx,OU=Groups,OU=Primary,OU=All,DC=mydomainname,DC=com)(memberof=CN=XxxxxxXXXx,OU=Groups,OU=Primary,OU=All,DC=mydomainname,DC=com)(memberof=CN=xxxxxxxxxxxxxx,OU=Groups,OU=Primary,OU=All,DC=mydomainname,DC=com)))"

Yeah, your ldapsearchfilter option is hitting the 256-byte MAX_TOKEN
limit in hba.c.  A one-line improvement would be to increase that
constant, but it doesn't look very much harder to get rid of that
fixed-size buffer altogether in favor of a StringInfo.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "Zechman, Derek S"
Date:
Subject: pg_hba.conf "authentication file token too long, skipping"
Next
From: Andres Martin del Campo Campos
Date:
Subject: Re: BUG #18027: Logical replication taking forever