# Anonymous Kibana Users

**URL:** <https://discuss.elastic.co/t/anonymous-kibana-users/270071>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [April 14, 2021, 12:35am UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071 "2021-04-14T00:35:53Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [April 22, 2021, 12:43pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/21 "2021-04-22T12:43:46Z")

</div>

Hey @alfredo.deluca ,

Sorry I'm not sure I completely understand what you mean. Maybe you can describe with a bit more details what you already have, what is working and what doesn't and how exactly.

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![caitlyn.carlisle](https://avatars.discourse-cdn.com/v4/letter/c/edb3f5/32.png) [@caitlyn.carlisle](https://discuss.elastic.co/u/caitlyn.carlisle)\
**Post date:** [April 22, 2021, 1:13pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/22 "2021-04-22T13:13:33Z")

</div>

Additionally, which roles should be used for the anonymous user, if I implement kibana\_admin it shares editing features and I am looking for a view only role.

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [April 22, 2021, 1:35pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/23 "2021-04-22T13:35:48Z")

</div>

> [@caitlyn.carlisle](#):
>
> Additionally, which roles should be used for the anonymous user, if I implement kibana\_admin it shares editing features and I am looking for a view only role.

Yeah, `kibana_admin` is **definitely** not something you'd want to give to anonymous users. You're supposed to create a dedicated role that grants only as much privileges as needed and it really depends on your particular use case, there is no one-fits-all role here.

Here is the very nice guide that can help you to get started: [Securing access to Kibana | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/tutorial-secure-access-to-kibana.html)

There are also some links that you can find useful:

- [Kibana role management | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/kibana-role-management.html)
- [Kibana privileges | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/kibana-privileges.html)
- [Spaces | Kibana Guide [master] | Elastic](https://www.elastic.co/guide/en/kibana/master/xpack-spaces.html)

And in general granting any of the built-in roles (`kibana_admin`, `superuser`, `kibana_system` etc.) to anonymous service account is a big NO-NO in most of the cases unless you completely understand what you're doing.

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![alfredo.deluca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alfredo.deluca/32/95381_2.png) [@alfredo.deluca](https://discuss.elastic.co/u/alfredo.deluca)\
**Post date:** [April 22, 2021, 2:42pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/24 "2021-04-22T14:42:05Z")

</div>

Hi Oleg. sorry! I will try to be more clear.  
Thanks to your info I was able to see the following  
 ![image.png](https://us1.discourse-cdn.com/elastic/original/3X/8/9/89beb0017a06166bd89a93862ad9a7820e4c5202.png)

Also I was able to have the public uRL feature, when I share a dashboard.  
The problem is if now we can embed a dashboard with users in the company without login/account for them, anyone in the world with the our kibana url can see  
 ![image.png](https://us1.discourse-cdn.com/elastic/original/3X/8/9/89beb0017a06166bd89a93862ad9a7820e4c5202.png)

then click on Continue as Guest, can see our dashboards and I would like to avoid that, actually management will not allow me to do so.  
So I wonder if it is possible to remove the **CONTINUE AS GUEST** selector but still sharing the dashboard with the public URL and without a login/account.

Cheers

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [April 22, 2021, 3:22pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/25 "2021-04-22T15:22:46Z")

</div>

> [@alfredo.deluca](#):
>
> So I wonder if it is possible to remove the **CONTINUE AS GUEST** selector but still sharing the dashboard with the public URL and without a login/account.

I see now, thanks. So yeah, you can hide `Continue as Guest` if you set [`showInSelector`](https://www.elastic.co/guide/en/kibana/current/security-settings-kb.html#authentication-provider-settings) config property of the _anonymous_ authentication provider to `false`.

> anyone in the world with the our kibana url can see

**But** `showInSelector: false` just hides this option from the Login Selector UI for convinience, anonymous access is still enabled and, as mentioned in [Authentication in Kibana | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/kibana-authentication.html#anonymous-authentication), anyone with access to the network Kibana is exposed to _technically_ (e.g. use the same URL that your `iframe` uses) will be able to access Kibana. If Kibana is exposed to Internet, then anyone in the world can use anonymous access to enter Kibana, that's why it's so crucial to properly setup roles and privileges for the anonymous service account.

If it's not something you expect then, unfortunately, anonymous access isn't what you need. The thing you'd need is Single-Sign On (SAML, OpenID Connect, whatever your users use to log in to your SharePoint website) then.

Best,  
Oleg

---

<div class="post-metadata">

**Author:** ![alfredo.deluca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alfredo.deluca/32/95381_2.png) [@alfredo.deluca](https://discuss.elastic.co/u/alfredo.deluca)\
**Post date:** [April 23, 2021, 7:49am UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/26 "2021-04-23T07:49:02Z")

</div>

thanks heaps. Oleg.  
Appreciated  
I will give it a try and see what they think. For now I will implement the showInSelector: false.  
Cheers and I will keep you posted

---

<div class="post-metadata">

**Author:** ![alfredo.deluca](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alfredo.deluca/32/95381_2.png) [@alfredo.deluca](https://discuss.elastic.co/u/alfredo.deluca)\
**Post date:** [April 27, 2021, 6:48pm UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/27 "2021-04-27T18:48:26Z")

</div>

Hi oleg.  
I was able to implement the anonymous user setup + not showing it on the login selector.

Of course I am aware of that is still a public url.  
Cheers

/Alf

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [April 28, 2021, 7:35am UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/28 "2021-04-28T07:35:10Z")

</div>

Thanks for the update, glad it worked out!

---

<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:** [May 26, 2021, 7:36am UTC](https://discuss.elastic.co/t/anonymous-kibana-users/270071/29 "2021-05-26T07:36:01Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/anonymous-kibana-users/270071.md?page=1)
