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.
Hi,
we tried to put a secondary security level on top of this plugin, more specifically, we put the access constraints to the auth and security indexes. So that we can control that no normal user can touch the security part. However, now we got the permission deny for all the writing access.
Maybe its the default thing that auth and security indexes are protected from 'user' role and we did the redundant thing that we shouldnt?
Thanks,
The text was updated successfully, but these errors were encountered:
curl -XPOST 'localhost:9200/security/constraint/' -d "{
"authenticator" : "index",
"paths" : ["/auth"],
"methods" : ["get", "post"],
"roles" : ["admin"]
}"
but then we got permission denied for any auth access even when we log in as 'admin' role.
I wonder what the general procedure is to protect the authentication index? It clearly is not desirable to allow users to access the index, so is the procedure described above the way to go?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
we tried to put a secondary security level on top of this plugin, more specifically, we put the access constraints to the auth and security indexes. So that we can control that no normal user can touch the security part. However, now we got the permission deny for all the writing access.
Maybe its the default thing that auth and security indexes are protected from 'user' role and we did the redundant thing that we shouldnt?
Thanks,
The text was updated successfully, but these errors were encountered: