On 13/01/2022 15:34, Shawn McKinney wrote:
On Jan 12, 2022, at 4:49 PM, Emmanuel Lécharny wrote:
Indeed, thus my question...
I will add some logs when an Undefined filter is found, so that at leats we
have some trace...
+ 1
A characteristic of a poor system is bad/unexpected things
> On Jan 12, 2022, at 4:49 PM, Emmanuel Lécharny wrote:
>
> Indeed, thus my question...
>
> I will add some logs when an Undefined filter is found, so that at leats we
> have some trace...
+ 1
A characteristic of a poor system is bad/unexpected things happening and we
have no idea why.
On 12/01/2022 21:52, Stefan Seelmann wrote:
I understand it the same way as you, especially the next paragraph makes
it clear that no error must be returned:
Servers MUST NOT return errors if attribute descriptions or matching
rule ids are not recognized, assertion values are
I understand it the same way as you, especially the next paragraph makes
it clear that no error must be returned:
Servers MUST NOT return errors if attribute descriptions or matching
rule ids are not recognized, assertion values are invalid, or the
assertion syntax is not supported.
Hi!
recently, I was working on fixing a NPE in the server. Thtis was due to
a wrong filter being sent, where a Substring filter was used for an
attribute that does not have a SunstringMR (uniqueMmeber).
The filter was like (uniqueMmeber=abc*).
RFC 4511 is not absolutely clear about what to
