# Kibana not working after installing FLX beta 2

**URL:** <https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333>\
**Category:** Search Guard\
**Created:** [July 4, 2022, 9:15am UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333 "2022-07-04T09:15:36Z")\
**Posts on this page:** 18\
**Page:** 2

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 5, 2022, 11:44am UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/21 "2022-07-05T11:44:00Z")

</div>

Please use `user_mapping.user_name.from` instead.

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 5, 2022, 11:55am UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/22 "2022-07-05T11:55:00Z")

</div>

Yay, that got me a bit further : now I see the login screen.  
However, I still can’t login:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/5/564e80da121a6439f330142512f0f97e4d7d5efd.png)

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 5, 2022, 12:00pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/23 "2022-07-05T12:00:04Z")

</div>

Then please activate the debug mode. You should get debug infos then directly on the login screen:

> **[Introduction to sg\_authc](https://docs.search-guard.com/flx/authentication-authorization-configuration#debugging-the-authc-configuration)**
>
> How to configure, mix and chain authentication and authorization domains for Search Guard.

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 5, 2022, 12:07pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/24 "2022-07-05T12:07:48Z")

</div>

Not much help, unfortunately

![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/7/75ad57bc82430576d2fce9cdd95dde79781444d5.png)

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 5, 2022, 12:10pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/25 "2022-07-05T12:10:01Z")

</div>

Can you then please check the ES logs again?

Sorry for the trouble.

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 5, 2022, 12:13pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/26 "2022-07-05T12:13:41Z")

</div>

Hmmm maybe that one:

```auto
{"type": "server", "timestamp": "2022-07-05T14:12:37,226+02:00", "level": "WARN", "component": "c.f.s.a.b.RequestAuthenticationProcessor", "cluster.name": "test", "node.name": "node42", "message": "Error while mapping auth credentials for trusted_origin[adca255d]", "cluster.uuid": "3LC10Pj8TTCaDX54FfnlrA", "node.id": "pZrWb7qMSP2-n4Jx86HZpA" ,
"stacktrace": ["com.floragunn.searchguard.authc.CredentialsException: No user name found",

```

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 5, 2022, 2:02pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/27 "2022-07-05T14:02:12Z")

</div>

I also tried `user_mapping.user_name.from: oidc.preferred_username`

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 6, 2022, 11:35am UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/28 "2022-07-06T11:35:41Z")

</div>

Hm, that log message indicates that `trusted_origin` auth domain could not find credentials. In the context of Kibana, that should be expected. So, I do not believe that the log message is related.

Can you raise the log level of `com.floragunn.searchguard.authc` to trace? From the command line, you can do this with:

```auto
curl --insecure -u admin:admin -X PUT "https://your-cluster:9200/_cluster/settings" -H "Content-Type: application/json" -d "{ \"transient\": { \"logger.com.floragunn.searchguard.authc\": \"trace\" } }"

```

If the volume is the logs is too large, don’t hesitate to send the the whole bunch to me by private message.

Also, can you also provide the Kibana log output again?

Thank you,

Nils

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 6, 2022, 12:39pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/30 "2022-07-06T12:39:28Z")

</div>

Ok, thanks for the information.

Could you please try the following sg\_frontend\_authc.yml config:

```auto
default:
  auth_domains:
  - type: "oidc"
    oidc.idp.openid_configuration_url: "..."
    oidc.client_id: "..."
    oidc.client_secret: "..."
    user_mapping.user_name.from: oidc_id_token.preferred_username
    user_mapping.roles.from: oidc_id_token.roles

```

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 6, 2022, 12:54pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/31 "2022-07-06T12:54:16Z")

</div>

yes, that made it go a bit further.  
Now we have another problem 🙂

 ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/d/d1b5c59241464875cfcca8aab2edd55d01f054ea.png)

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 6, 2022, 1:12pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/32 "2022-07-06T13:12:48Z")

</div>

oh ☹

What is the order in which you initialize the nodes of your cluster? In your elasticsearch.yml, do you use any of the `gateway.*` options?

Could you try to restart your master node to check whether this fixes things?

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 6, 2022, 1:18pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/33 "2022-07-06T13:18:58Z")

</div>

Restarting the master node and kibana did the trick.  
I’m not using any `gateway` options in `elasticsearch.yml`.  
Oh noes, now we have another problem:  
 ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/0/07b1bce6b133da33b331c7607ac12d013f60a61a.png)

🤣

Thanks Nils, for your patience and hard work at getting this to work in our environment !

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 6, 2022, 1:20pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/34 "2022-07-06T13:20:26Z")

</div>

Joke aside, what needs to be done here now ?  
Fix the migration script I guess. Do you want me to open an issue on gitlab? [search-guard / sgctl · GitLab](https://git.floragunn.com/search-guard/sgctl) ?

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 6, 2022, 1:24pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/35 "2022-07-06T13:24:46Z")

</div>

> [@faxmodem](#):
>
> Oh noes, now we have another problem:  
> ![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/2X/0/07b1bce6b133da33b331c7607ac12d013f60a61a.png)

This is easy to fix. Add to your `kibana.yml` this:

```auto
security.showInsecureClusterWarning: false

```

> [@faxmodem](#):
>
> Joke aside, what needs to be done here now ?  
> Fix the migration script I guess. Do you want me to open an issue on gitlab? [search-guard / sgctl · GitLab](https://git.floragunn.com/search-guard/sgctl) ?

We are already working on that, so it is not really necessary. Thank you for the offer, anyway!

If you don’t mind I would provide you a new snapshot version of Search Guard to check whether the issue with the `.searchguard_sessions` index can be fixed without having to manually restart the master node. This, however, will take one or two days.

> [@faxmodem](#):
>
> Thanks Nils, for your patience and hard work at getting this to work in our environment !

Thank you for your patience! This direct feedback is the most valuable information we can have in order to straighten out things.

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 6, 2022, 1:27pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/36 "2022-07-06T13:27:01Z")

</div>

FWIW the cluster has currently one OS node and all the others are ES

---

<div class="post-metadata">

**Author:** ![nils](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nils](https://forum.search-guard.com/u/nils)\
**Post date:** [July 6, 2022, 1:30pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/37 "2022-07-06T13:30:07Z")

</div>

Cool, interesting setup! We would love to learn about your experience with this.

---

<div class="post-metadata">

**Author:** ![faxmodem](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/faxmodem/32/22_2.png) [@faxmodem](https://forum.search-guard.com/u/faxmodem)\
**Post date:** [July 6, 2022, 1:32pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/38 "2022-07-06T13:32:34Z")

</div>

well, the idea is to migrate to Opensearch. So we’re waiting for OS support to be stable, so we can migrate all our production clusters, hence the experimentation with flx beta2 and this discussion 🙂

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/system/32/1870_2.png) [@system](https://forum.search-guard.com/u/system)\
**Post date:** [July 27, 2022, 1:32pm UTC](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333/39 "2022-07-27T13:32:57Z")

</div>

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

[Previous page](https://forum.search-guard.com/t/kibana-not-working-after-installing-flx-beta-2/2333.md?page=1)