Re: ITS#8286 pending questions

Quanah Gibson-Mount wrote: > I've done a first pass through the source tree adding missing matching > rules to the olc* attributes to address ITS#8286 > ().  However, > many of the attributes are string types, and can either be case > exact/i

Re: ITS#8286 pending questions

Michael Ströder wrote: Quanah Gibson-Mount wrote: I've done a first pass through the source tree adding missing matching rules to the olc* attributes to address ITS#8286 (). However, many of the attributes are string types, and can either

Re: ITS#8286 pending questions

Some more comments on a sub-set of the attributes. Quanah Gibson-Mount wrote: > olcReferral -- case ignore match? It's already declared SUP labeledURI and therefore has caseExactMatch. This makes sense because it could specify an LDAPI URL with case-sensitive socket path name. > olcRootPw -- cas

Re: ITS#8286 pending questions

Howard Chu wrote: > Michael Ströder wrote: >> Quanah Gibson-Mount wrote: >>> servers/slapd/bconfig.c --- >>> olcInclude -- case ignore match? >> >> Is already defined with caseExactMatch via "SUP labeledURI". >> IMO deriving from labeledURI does not make sense t

Re: ITS#8286 pending questions

--On Wednesday, May 30, 2018 11:40 AM +0200 Michael Ströder wrote: Some more comments on a sub-set of the attributes. Thanks! On the attributes related to filesystem paths (logfile, etc), I was going with case ignore match since olcConfigFile and olcArgsFile are already caseIgnoreMatch.

cn=config schema, matching rules and UX with web2ldap

HI! I'd like to highlight a bit why I'm nitpicking on schema definitions for back-config and how careful schema crafting can help to have a better UX with less effort (even though I'm personally using back-config read-only for monitoring). The goals of web2dap are: 1. guide the user to do i