[Self-managed]: Kibana enrollment token is already expired on fresh elasticsearch setup(before 30 minutes).

[amolnater-qasource]

Kibana version: 8.1 BC-3 Kibana self-managed environment

Host OS and Browser version: All, All

Build details:

BUILD: 50346
COMMIT: 0335dd6a26ef29ae9021d0fae9347dc88f3b7d6e
Artifact Link: https://staging.elastic.co/8.1.0-bee672a6/summary-8.1.0.html

Preconditions:

1. Elasticsearch and kibana should be extracted.

Steps to reproduce:

1. Login to Kibana environment.

2. Run elasticsearch.bat and observe all required configurations are available.
   

3. Run kibana.bat and get the url to configure kibana.

4. Navigate to the url and add kibana enrollment token (before 30 minutes).

5. Observe Generate a new enrollment token error.

Expected Result:
Kibana enrollment token should not be already expired on fresh elasticsearch setup(before 30 minutes).

• As per last information pre-generated token can be used for 30 minutes.

Screenshot:

Note:

• Issue is reproduced on 4 different environment setups.

reviewed and assigned to @jkakavas

[jkakavas]

Are kibana and elasticsearch on the same server ?

…

On Thu, 17 Feb 2022 at 10:53 AM, karanbir singh ***@***.***> wrote: Assigned #125908 <#125908> to @jkakavas <https://github.com/jkakavas>. — Reply to this email directly, view it on GitHub <#125908 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOOCKFX66XAWTUIUUA7KHLU3SZSDANCNFSM5OT724MQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were assigned.Message ID: ***@***.***>

[amolnater-qasource]

Hi @jkakavas
Yes! we were setting up kibana with the same steps as we were installing on earlier builds.

• Extracted elasticsearch and kibana artifacts in C:\elk folder.
• Run elasticsearch and kibana.
• And within 5-10 minutes we used the enrollment token for kibana setup.

Thanks

[jkakavas]

Thanks for catching this @amolnater-qasource ! This is a valid bug and we are fixing it with elastic/elasticsearch#84096

[amolnater-qasource]

Hi @jkakavas
We have revalidated this issue on 8.1 BC4 self-managed environment and found it fixed now.

• Kibana enrollment token is not already expired on fresh elasticsearch setup(before 30 minutes).
• Kibana setup is successful with enrollment token available in elasticsearch configuration.

Build details:
VERSION: 8.1.0
BUILD: 50428
COMMIT: 015578b
Artifact Link: https://staging.elastic.co/8.1.0-bb72bc41/summary-8.1.0.html

Hence we are closing this.
Thanks

[jkakavas]

* Kibana enrollment token is not already expired on fresh elasticsearch setup(before 30 minutes).

For the sake of clarity and future reference, the problem was not that the enrollment token was expired. It was created in a way that made it invalid (but not expired) due to a recent refactoring in Elasticsearch.

[amolnater-qasource]

Thanks for the information!