# Security error when create new role with field\_security

**URL:** <https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring, elastic-stack-security\
**Created:** [December 9, 2020, 7:03am UTC](https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082 "2020-12-09T07:03:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thejusjose-mindcurv](https://avatars.discourse-cdn.com/v4/letter/t/9fc348/32.png) [@thejusjose-mindcurv](https://discuss.elastic.co/u/thejusjose-mindcurv)\
**Post date:** [December 9, 2020, 7:03am UTC](https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082/1 "2020-12-09T07:03:30Z")

</div>

Hi Team,

We have Kibana version 7.8 installed.

Tried to hide some particular fields for kibana users by creating a new custom role after referring [https://www.elastic.co/guide/en/elasticsearch/reference/7.8/field-level-security.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/field-level-security.html)

In Kibana Dev-Tools ::

POST /\_security/role/new-custom-role-name  
{  
"indices": [  
{  
"names": ["index-name-\*"],  
"privileges": ["read"],  
"field\_security" : {  
"grant" : ["category", "@timestamp", "message"]  
}  
}

Output ::

"error" : {  
"root\_cause" : [  
{  
"type" : "security\_exception",  
"reason" : "current license is non-compliant for [field and document level security]",  
"license.expired.feature" : "field and document level security"  
}  
],  
"type" : "security\_exception",  
"reason" : "current license is non-compliant for [field and document level security]",  
"license.expired.feature" : "field and document level security"  
},  
"status" : 403  
}

Could someone be able to guide on how to overcome and achieve this (hide some particular fields for kibana users) ?

---

<div class="post-metadata">

**Author:** ![Mikel\_U](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikel_u/32/79306_2.png) [@Mikel\_U](https://discuss.elastic.co/u/Mikel_U)\
**Post date:** [December 9, 2020, 7:58am UTC](https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082/2 "2020-12-09T07:58:54Z")

</div>

Hello,

You have a similar issue here:

> [@Filed Security For Gold Membership](https://discuss.elastic.co/t/filed-security-for-gold-membership/171951):
>
> Hi Team, I want to provide the field level security , but when i am creating the role with below POST API call , POST /\_xpack/security/role/offshoreRole { "indices": [{ "names" : ["logstash-",".kibana"], "privileges" : ["read"], "field\_security" : { "grant" : ["\*"], "except": ["abc","xyz"] } } ] } I am getting { "error": { "root\_cause": [{ "type": "security\_exception", "reason": "current license is non-compliant for [field and document level security]", "license.ex…

I hope it will help.

---

<div class="post-metadata">

**Author:** ![thejusjose-mindcurv](https://avatars.discourse-cdn.com/v4/letter/t/9fc348/32.png) [@thejusjose-mindcurv](https://discuss.elastic.co/u/thejusjose-mindcurv)\
**Post date:** [December 10, 2020, 6:23pm UTC](https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082/3 "2020-12-10T18:23:02Z")

</div>

Hi Mikel,

Thanks for the update.

Seems we need Platinum subscription for the same.

Could you let me know if there is any other alternative method to achieve this. i.e. to hide some particular fields for kibana users. ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 7, 2021, 6:23pm UTC](https://discuss.elastic.co/t/security-error-when-create-new-role-with-field-security/258082/4 "2021-01-07T18:23:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.