{"action":"created","issue":{"url":"https://api.github.com/repos/floragunncom/search-guard/issues/105","repository_url":"https://api.github.com/repos/floragunncom/search-guard","labels_url":"https://api.github.com/repos/floragunncom/search-guard/issues/105/labels{/name}","comments_url":"https://api.github.com/repos/floragunncom/search-guard/issues/105/comments","events_url":"https://api.github.com/repos/floragunncom/search-guard/issues/105/events","html_url":"https://github.com/floragunncom/search-guard/issues/105","id":140786123,"number":105,"title":"DLS user_roles not working properly","user":{"login":"Tawel","id":12673619,"avatar_url":"https://avatars.githubusercontent.com/u/12673619?v=3","gravatar_id":"","url":"https://api.github.com/users/Tawel","html_url":"https://github.com/Tawel","followers_url":"https://api.github.com/users/Tawel/followers","following_url":"https://api.github.com/users/Tawel/following{/other_user}","gists_url":"https://api.github.com/users/Tawel/gists{/gist_id}","starred_url":"https://api.github.com/users/Tawel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tawel/subscriptions","organizations_url":"https://api.github.com/users/Tawel/orgs","repos_url":"https://api.github.com/users/Tawel/repos","events_url":"https://api.github.com/users/Tawel/events{/privacy}","received_events_url":"https://api.github.com/users/Tawel/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-14T20:18:52Z","updated_at":"2016-05-01T11:22:19Z","closed_at":"2016-05-01T11:22:19Z","body":"I'm trying to create an authorization mechanism with searchguard to an elastic index.\r\nI am doing it by having a field on each entry that specifies which roles can see the entry (may have several roles specifed). Then using the user_roles DLS filter, Im filtering out the entries that the user cannot see and returning only those he can based on the roles he has.\r\nDoing it i noticed that the DLS filter doesn't work when the DLS term has a hyphen or even capital letter. So for example if I have a role named \"crazy-role\" (or crazyRole) and obviously a field on some entries with the value \"crazy-role\" the DLS filter won't filter the documents accordingly.\r\nFor a role named \"crazy_role\" or \"role\" it works fine.\r\nIt is inconvenient and i hope you will fix it soon."},"comment":{"url":"https://api.github.com/repos/floragunncom/search-guard/issues/comments/216035667","html_url":"https://github.com/floragunncom/search-guard/issues/105#issuecomment-216035667","issue_url":"https://api.github.com/repos/floragunncom/search-guard/issues/105","id":216035667,"user":{"login":"floragunncom","id":11678154,"avatar_url":"https://avatars.githubusercontent.com/u/11678154?v=3","gravatar_id":"","url":"https://api.github.com/users/floragunncom","html_url":"https://github.com/floragunncom","followers_url":"https://api.github.com/users/floragunncom/followers","following_url":"https://api.github.com/users/floragunncom/following{/other_user}","gists_url":"https://api.github.com/users/floragunncom/gists{/gist_id}","starred_url":"https://api.github.com/users/floragunncom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/floragunncom/subscriptions","organizations_url":"https://api.github.com/users/floragunncom/orgs","repos_url":"https://api.github.com/users/floragunncom/repos","events_url":"https://api.github.com/users/floragunncom/events{/privacy}","received_events_url":"https://api.github.com/users/floragunncom/received_events","type":"User","site_admin":false},"created_at":"2016-05-01T11:22:19Z","updated_at":"2016-05-01T11:22:19Z","body":"Auto close this issue because it refers to Search Guard 1 which is decommissioned now. For details pls. see https://github.com/floragunncom/search-guard-attic/wiki . If this issue is still valid for Search Guard 2 (for elasticsearch 2.x) feel free to reopen it (or to file a new one). Pls. do not longer report issues for Search Guard 1 (for elasticsearch 1.x). We sincerely apologize for the inconvenience this may have caused. Thanks for contributing!"}}