# パスワード変更の禁止 **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security\ **Created:** [February 13, 2021, 11:05am UTC](https://discuss.elastic.co/t/topic/264210 "2021-02-13T11:05:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![nickofthyme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickofthyme/32/60032_2.png) [@nickofthyme](https://discuss.elastic.co/u/nickofthyme)\ **Post date:** [March 5, 2021, 7:46pm UTC](https://discuss.elastic.co/t/topic/264210/2 "2021-03-05T19:46:02Z")
> [Translated] How can I prevent the user from going to the Account Settings page in the figure when logging in with an account named A that has [kibana\_dashboard\_only\_user]? Finally, I want to prevent the password from being changed. Also, NGINX is used as a reverse proxy. version is 6.8.13 and the license is Basic. The short answer is no. I tried a few hacks to see if I could do what you are asking for but in the end, I found no solution. This functionality is by design and admins are not meant to forbid access to a user changing their own password. User password hashes are stored in the `.security*` indices which are used by the security module to provide security features for ES (see [discussion](https://discuss.elastic.co/t/what-does-restricted-indices-means-in-security-has-privileges-api/185175/2)). Non-super users are not granted access to restricted indices unless the [`allow_restricted_indices`](https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#CO530-5) flag is set to true on the [Indices Privileges](https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv) which is inadvisable. > Restricted indices are a special category of indices that are used internally to store configuration data. Only internal system roles should normally grant privileges over the restricted indices. **Toggling this flag is most discouraged because it could effectively grant superuser privileges.** If however, for administrative purposes, you need to create a role with privileges covering restricted indices, you must set this field to `true` (default is `false` ), and then the `names` field will cover the restricted indices as well. There may be a way to achieve this through some custom [application privilege](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/security-privileges.html#application-privileges) or indices privilege assigned to a custom [elasticsearch role](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/security-api-put-role.html) but those rules require [`privileges`](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/security-privileges.html#privileges-list-indices) that are all meant to allow access not deny. In this case, the user already does **not** have access to the restricted indices except for their own credentials. Hope that helps. --- _[View the full topic](https://discuss.elastic.co/t/topic/264210)._