You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.
I am using the bro framework to gather data and store them in the database.
Bro creates indices like "bro-201408220900".
I tried to use a star as wildcard, to restrict access to the bro related fields like that:
POST /security/constraint/
{
"authenticator" : "index",
"paths" : ["bro-*"],
"methods" : ["get", "post"],
"roles" : ["admin"]
}
Is this even possible to use such wildcards for content constraints or do I use them wrong?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using the bro framework to gather data and store them in the database.
Bro creates indices like "bro-201408220900".
I tried to use a star as wildcard, to restrict access to the bro related fields like that:
POST /security/constraint/
{
"authenticator" : "index",
"paths" : ["bro-*"],
"methods" : ["get", "post"],
"roles" : ["admin"]
}
Is this even possible to use such wildcards for content constraints or do I use them wrong?
The text was updated successfully, but these errors were encountered: