Re: Custom oauth validator options

> On 10 Oct 2026, at 12:12, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:

> I think this matters a bit more than for the builtin options, because
> unknown validator.* names can't be detected at reload time, and the
> view is the only place where an admin can see what the server actually
> parsed. The values still won't go through validations, e.g. in the
> above example typo will be simply displayed, but I think that's
> already better than hiding them and is worth doing.

Agreed, I think this is quite important and we should get that done before 19
ships. I'll get to reviewing this tomorrow.

> The attached patch emits them as validator.<name>=<value>, in the
> order they appear on the line. Since there's no limit on how many
> options a line can have, the fixed MAX_HBA_OPTIONS array doesn't work
> anymore, so options are sized dynamically now (MAX_HBA_OPTIONS plus
> the number of validator options).

I'm not crazy about this part though, I wonder if we should to put a hard cap
with a ... or something? I'll see what I can come up with.

--
Daniel Gustafsson