Filters should be case sensitive or not?

[leodido]

Sorry guys I forgot whether the filters MUST be case sensitive or not.

The following one DOES NOT work.

?filter=username eq "leodido@example.com" AND password eq "3d$h33ran"

The server returns:

{
	"schemas": [
		"urn:ietf:params:scim:api:messages:2.0:Error"
	],
	"status": 400,
	"scimType": "invalidFilter",
	"detail": "Filter is invalid: syntax error at character 33, mismatched input ' ' expecting <EOF>"
}null

(notice the null, there is somewhere a return missing in the error check conditions within the server, too).

Rather the following one works:

?filter=username eq "leodido@example.com" and password eq "3d$h33ran".

[samechelon]

I believe the error it's given by "AND", it should be lowercase

[leodido]

@samechelon I know the error cause is the uppercase operator. Infact I was asking if it's right that it gives an error or not?

Reformulating: the operators HAVE TO be lowercase by spec?

[alelb]

Attributes names and attribute operators used in filter are case insensitive (refs). So this is a bug.