When restart kibana, it shows "Could not locate that index-pattern" about for-elasticsearch-docs HOT 6 CLOSED

Hi @scf0920, this sounds like a permissions issue. Can you log in as admin and check the permissions for someone under Role Mappings? Then check to make sure those roles have the basic permissions you might need?

from for-elasticsearch-docs.

@aetter But it works well until kibana was restarted. And the API returns the correct results.
My security config:
Roles:

Role Map:

Users:

My solution:

1. export all Saved Objects as a.json file
2. delete .kibana__someone
3. log back in someone
4. import a.json into Saved Objects

Everything was back to normal...
I think it's kibana security plugin's bug. It's going to reproduce 100%. Please try to reproduce.
Thanks.

from for-elasticsearch-docs.

@aetter can you reproduce it?

from for-elasticsearch-docs.

Hi @scf0920, unfortunately, no, I can't reproduce your error.

• When I log in with someone, I'm unable to create an index pattern, because I can't read any data (as expected).
• When I have the administrator add an index called someone, I still can't create an index pattern. (See image.)

• When I map someone to kibana_user, now I can create the index pattern, but I can't do much else (as expected).
• When I docker-compose stop and docker-compose start and log in as someone, I still have my index pattern.

Can you reproduce from a brand new 0.8.0 cluster? If so, can you post your docker-compose.yml and the start to finish steps?

from for-elasticsearch-docs.

@aetter Very thanks.. I finally found the reason...
Before:

After I change:

Then I log in as someone, my index pattern back to normal...
In a word, someone has miss index permissions of .kibana_xxxxxx_someone_2. But I think it should be automatic...
You can map someone to my own_index and see if you can reproduce.

from for-elasticsearch-docs.

Hi @scf0920, yeah, I think that's a suggestion worth discussing in a broader forum. I'm closing this issue, but opened https://github.com/opendistro-for-elasticsearch/security/issues/31 so that we can discuss if there are any negative side effects to making this sort of change. Thanks a bunch!

from for-elasticsearch-docs.