From: | mahendrakar s <mahendrakarforpg(at)gmail(dot)com> |
---|---|
To: | daniel(at)yesql(dot)se |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Subject: | Re: Increase limit on max length of the password( pg versions < 14) |
Date: | 2023-07-18 11:23:00 |
Message-ID: | CABkiuWrygk1ZcTFWBBqERr6RLwaKuNsdP_jguQ7KZ=02w3DOWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Access token length with bare minimal claims is more than 1000 in this case.
Workarounds are not possible in production.
On Tue, 18 Jul 2023 at 15:10, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 18 Jul 2023, at 11:30, mahendrakar s <mahendrakarforpg(at)gmail(dot)com> wrote:
>
> > So we have two options:
> > 1. Backport patch[1] to 11,12,13
> > 2. Change ONLY the limit on the max length of the password(my patch attached).
>
> We typically only backpatch bugfixes and not functional changes, and this seems
> to fall in the latter category.
>
> As the size of the JWT depends on the number of claims in it, are you able to
> reduce the number of claims to stay under the limit as a workaround?
>
> --
> Daniel Gustafsson
>
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2023-07-18 12:12:45 | Re: Increase limit on max length of the password( pg versions < 14) |
Previous Message | Sofia Kopikova | 2023-07-18 11:19:46 | Re: Add TOAST support for more system tables |