1 of 1 people found this helpful
A rule is an object that can contain multiple lists
You can create a list of list names (just a list of strings), but I dont think thats what you want.
What's the problem you're trying to solve? It is possible to reference a list by name -- dynamically in the rules. See below rules, they are all effectively the same but reference the list in a different way.
Well, I'm really lazy and when creating rule criteria I'd like to use multiple lists within one criteria, something like when you create category list, just choosing which categories should be in the list and then using it in rule criteria.
You're not lazy, you just want to be more efficient.
This seems like a cool idea, however its' not possible in the UI.
Using the REST interface, you could go crazy with it though.
Ok, thanks Jon for your insight ;-)
Just tried to access the REST interface but somehow I'm failing to authenticate. I'm sure that my credentials are OK, also my account has REST enabled and it's enabled under User Interface.
$ curl -k -i -X POST "$REST/login?userName=XXXXXX&pass=XXXXXX"
HTTP/1.1 401 Unauthorized
X-XSS-Protection: 1; mode=block
Date: Fri, 11 Aug 2017 09:45:09 GMT
Check username and password
Any idea what I might doing wrong?
You forgot to create a cookie store (maybe)? Here's what I use:
curl -ki -c cookies.txt -X POST "$REST/login?userName=USERNAME&pass=PASSWORD"
curl -ki -b cookies.txt "$REST/list"
I guess that I don't need to create cookies storage if I try to just log in(?).
Anyway I've tried your command but still getting the 401 when trying to POST my credentials :-(
Could the password have some strange character which could get messed up on the CLI?
As a test you could create a user with API permissions with a simpler password and try with that account.
Thanks Jon, I had special char in my password, removing it helped. But it was not that special, kind of weird it couldn't take it, it was just one '#".