# Service account token elastic/kibana problemKibana not accessible from browser
**URL:** https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333
**Category:** Kibana
**Created:** [October 24, 2022, 3:39pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333 "2022-10-24T15:39:21Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@EExisT](https://discuss.elastic.co/u/EExisT)
#### Post date: [October 24, 2022, 3:39pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/1 "2022-10-24T15:39:21Z")
Hello,
I was trying to start Kibana as a service, but I noticed that after a few seconds from the start Kibana goes down.
In the /var/log/syslog file I saw this error:
```auto
Oct 24 17:24:18 ubuntu-linux-22-04-desktop kibana[40582]: FATAL Error: [config validation of [elasticsearch].u
sername]: value of "elastic" is forbidden. This is a superuser account that cannot write to system indices that
Kibana needs to function. Use a service account token instead. Learn more: https://www.elastic.co/guide/en/elast
icsearch/reference/8.0/service-accounts.html
```
So I'm trying to configure the service account token for the service account elastic/kibana.
I give this command to produce the following value for my token:
```auto
root@ubuntu-linux-22-04-desktop:/usr/share/elasticsearch/bin# ./elasticsearch-service-tokens create elastic/kibana kibana_token-1
SERVICE_TOKEN elastic/kibana/kibana_token-1 = AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE
```
And when I try to visualise the file "service\_tokens" I got this:
```auto
root@ubuntu-linux-22-04-desktop:/usr/share/elasticsearch/bin# cat /etc/elasticsearch/service_tokens
elastic/kibana/kibana_token-1:{PBKDF2_STRETCH}10000$nzu5ZW87KX0Q6woAMwhRvqftgx04vBjH2JbDV3xGWIA=$PKXIPPD2EbrKGjNidZ69YzZ6ydmyTzkY1xPm2EGD79Y=
```
that is different from the previous value I got from the prompt.
I tried both values to understand If kibana could connect to ES, but I receive always the same error.
```auto
root@ubuntu-linux-22-04-desktop:/etc/elasticsearch# curl -H "Authorization: Bearer AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE" https://10.211.55.7:9200/_cluster/health
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
ES
```auto
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
network.host: 10.211.55.7
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["node-1"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# --------------------------------- Readiness ----------------------------------
#
# Enable an unauthenticated TCP readiness endpoint on localhost
#
#readiness.port: 9399
#
# ---------------------------------- Various -----------------------------------
#
# Allow wildcard deletion of indices:
#
#action.destructive_requires_name: false
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically
# generated to configure Elasticsearch security features on 19-10-2022 13:57:07
#
# --------------------------------------------------------------------------------
# Enable X-Pack security features
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
#xpack.security.http.ssl:
# enabled: true
# keystore.path: certs/http.p12
# Enable encryption and mutual authentication between cluster nodes
#xpack.security.transport.ssl:
# enabled: true
# verification_mode: certificate
# keystore.path: certs/transport.p12
# truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
#cluster.initial_master_nodes: ["ubuntu-linux-22-04-desktop"]
# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0
# Allow other nodes to join the cluster from anywhere
# Connections are encrypted and mutually authenticated
#transport.host: 0.0.0.0
# Transport layer
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.key: /etc/elasticsearch/Elastic_CERTS/elasticsearch.key
xpack.security.transport.ssl.certificate: /etc/elasticsearch/Elastic_CERTS/elasticsearch.crt
xpack.security.transport.ssl.certificate_authorities: ["/etc/elasticsearch/Elastic_CERTS/ca/ca.crt"]
# HTTP layer
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.verification_mode: certificate
xpack.security.http.ssl.key: /etc/elasticsearch/Elastic_CERTS/elasticsearch.key
xpack.security.http.ssl.certificate: /etc/elasticsearch/Elastic_CERTS/elasticsearch.crt
xpack.security.http.ssl.certificate_authorities: ["/etc/elasticsearch/Elastic_CERTS/ca/ca.crt"]
#----------------------- END SECURITY AUTO CONFIGURATION -------------------------
```
Kibana
```auto
# For more configuration options see the configuration guide for Kibana in
# https://www.elastic.co/guide/index.html
# =================== System: Kibana Server ===================
# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601
# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "10.211.55.7"
# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""
# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# Defaults to `false`.
#server.rewriteBasePath: false
# Specifies the public URL at which Kibana is available for end users. If
# `server.basePath` is configured this URL should end with the same basePath.
#server.publicBaseUrl: ""
# The maximum payload size in bytes for incoming server requests.
#server.maxPayload: 1048576
# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"
# =================== System: Kibana Server (Optional) ===================
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
# These settings enable SSL for outgoing requests from the Kibana server to the>
server.ssl.enabled: true
server.ssl.certificate: "/etc/kibana/certs/kibana.crt"
server.ssl.key: "/etc/kibana/certs/kibana.key"
# =================== System: Elasticsearch ===================
# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["https://10.211.55.7:9200"]
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/ca/ca.crt"]
elasticsearch.ssl.certificate: "/etc/kibana/certs/kibana.crt"
elasticsearch.ssl.key: "/etc/kibana/certs/kibana.key"
# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
# Elastic Credentials
#The xpack.security.enabled setting no longer exists in Kibana 8.X.X
#xpack.security.enabled: true
elasticsearch.username: "elastic"
elasticsearch.password: "+hvLtT0MMhiqZu_D6_uL"
# Kibana can also authenticate to Elasticsearch via "service account tokens".
# Service account tokens are Bearer style tokens that replace the traditional username/password based configurat
ion.
# Use this token instead of a username/password.
# elasticsearch.serviceAccountToken: "my_token"
# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500
# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000
# The maximum number of sockets that can be used for communications with elasticsearch.
# Defaults to `Infinity`.
#elasticsearch.maxSockets: 1024
# Specifies whether Kibana should use compression for communications with elasticsearch
# Defaults to `false`.
#elasticsearch.compression: false
# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]
# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}
# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 30000
# =================== System: Elasticsearch (Optional) ===================
# These files are used to verify the identity of Kibana to Elasticsearch and are required when
# xpack.security.http.ssl.client_authentication in Elasticsearch is set to required.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key
# Enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]
# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
# =================== System: Logging ===================
# Set the value of this setting to off to suppress all logging output, or to debug to log everything. Defaults t
o 'info'
#logging.root.level: debug
# Enables you to specify a file where Kibana stores log output.
logging:
appenders:
file:
type: file
fileName: /var/log/kibana/kibana.log
layout:
type: json
root:
appenders:
- default
- file
# layout:
# type: json
# Logs queries sent to Elasticsearch.
#logging.loggers:
# - name: elasticsearch.query
# level: debug
# Logs http responses.
#logging.loggers:
# - name: http.server.response
# level: debug
# Logs system usage information.
#logging.loggers:
# - name: metrics.ops
# level: debug
# =================== System: Other ===================
# The path where Kibana stores persistent data not saved in Elasticsearch. Defaults to data
#path.data: data
# Specifies the path where Kibana creates the process ID file.
pid.file: /run/kibana/kibana.pid
# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000ms.
#ops.interval: 5000
# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English (default) "en", Chinese "zh-CN", Japanese "ja-JP", French "fr-F
R".
#i18n.locale: "en"
# =================== Frequently used (Optional)===================
# =================== Saved Objects: Migrations ===================
# Saved object migrations run at startup. If you run into migration-related issues, you might need to adjust the
se settings.
# The number of documents migrated at a time.
# If Kibana can't start up or upgrade due to an Elasticsearch `circuit_breaking_exception`,
# use a smaller batchSize value to reduce the memory pressure. Defaults to 1000 objects per batch.
#migrations.batchSize: 1000
# The maximum payload size for indexing batches of upgraded saved objects.
# To avoid migrations failing due to a 413 Request Entity Too Large response from Elasticsearch.
# This value should be lower than or equal to your Elasticsearch cluster’s `http.max_content_length`
# configuration option. Default: 100mb
#migrations.maxBatchSizeBytes: 100mb
# The number of times to retry temporary migration failures. Increase the setting
# if migrations fail frequently with a message such as `Unable to complete the [...] step after
# 15 attempts, terminating`. Defaults to 15
#migrations.retryAttempts: 15
# =================== Search Autocomplete ===================
# Time in milliseconds to wait for autocomplete suggestions from Elasticsearch.
# This value must be a whole number greater than zero. Defaults to 1000ms
#unifiedSearch.autocomplete.valueSuggestions.timeout: 1000
# Maximum number of documents loaded by each shard to generate autocomplete suggestions.
# This value must be a whole number greater than zero. Defaults to 100_000
#unifiedSearch.autocomplete.valueSuggestions.terminateAfter: 100000
```
Now I'm trying to understand how service accounts work, and how can I add the service account token and the service account in the .tml files.
And why I'm receiving the last error when I try to curl es, when the certificates and public/private keys are configured.
Thank u very much
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [October 24, 2022, 3:59pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/2 "2022-10-24T15:59:55Z")
> [@EExisT](#):
>
> ```auto
> root@ubuntu-linux-22-04-desktop:/etc/elasticsearch# curl -H "Authorization: Bearer AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE" https://10.211.55.7:9200/_cluster/health
>
> ```
That is a cert issue... nothing to do with the token...
`-k` means ignore the certificate verification.
`curl -k -H "Authorization: Bearer AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE" https://10.211.55.7:9200/_cluster/health`
Did you try just to set the service token in the kibana.yml as it was outputed to the screen.
`elasticsearch.serviceAccountToken: "AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE"`
then comment out.
```auto
#elasticsearch.username: "elastic"
#elasticsearch.password: "+hvLtT0MMhiqZu_D6_uL"
```
All this would have been done for you if you just set up both elasticsearch and kibana using the default install process.
---
### Author:  [@EExisT](https://discuss.elastic.co/u/EExisT)
#### Post date: [October 24, 2022, 5:34pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/3 "2022-10-24T17:34:30Z")
Now it seems to stay running.
But why have I certificate issues?
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [October 24, 2022, 5:39pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/4 "2022-10-24T17:39:04Z")
> [@EExisT](#):
>
> Now it seems to stay running.
Good!
> [@EExisT](#):
>
> But why have I certificate issues?
You have self signed to you either need to use the `--cacert` option in `curl` or `-k`
You might need to read up on self signed certificates
---
### Author:  [@EExisT](https://discuss.elastic.co/u/EExisT)
#### Post date: [October 24, 2022, 6:19pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/5 "2022-10-24T18:19:52Z")
> [@stephenb](#):
>
> You have self signed to you either need to use the `--cacert` option in `curl` or `-k`
You are right, I will do it.
I tried, just to make sure, this command:
```auto
curl -k -H "Authorization: Bearer AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE" https://10.211.55.7:9200/_cluster/health
```
And I receive this error:
```auto
root@ubuntu-linux-22-04-desktop:/var/log/kibana# curl -k -H "Authorization: Bearer AAEAAWVsYXN0aWMva2liYW5hL2tpYmFuYV90b2tlbi0xOk51WGNnUUxnUlVHckhYNTRlc2RXQlE" https://10.211.55.7:9200/_cluster/health
{"error":{"root_cause":[{"type":"security_exception","reason":"failed to authenticate service account [elastic/kibana] with token name [kibana_token-1]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}}],"type":"security_exception","reason":"failed to authenticate service account [elastic/kibana] with token name [kibana_token-1]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401}root@ubuntu-linux-22-04-desktop:/va
{"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.4.0"},"@timestamp":"2022-10-24T19:51
:06.758+02:00","message":"Timeout: it took more than 1200000ms","error":{"message":"Timeout: it took more than 1
200000ms","type":"Error","stack_trace":"Error: Timeout: it took more than 1200000ms\n at Timeout._onTimeout (
/usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_plugin_service/resource_installer.js:61:20)\n
at listOnTimeout (node:internal/timers:559:17)\n at processTimers (node:internal/timers:502:7)"},"log":{"lev
el":"ERROR","logger":"plugins.ruleRegistry"},"process":{"pid":54698},"trace":{"id":"1f47962d84a20fd4ae28c2a8bc71
7ee2"},"transaction":{"id":"e76cb301d70c5590"}}
```
I tried by browser and I GET a 200 response from ES, so I think the service token authentication works...
Thanks @stephenb
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 21, 2022, 6:19pm UTC](https://discuss.elastic.co/t/service-account-token-elastic-kibana-problemkibana-not-accessible-from-browser/317333/6 "2022-11-21T18:19:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.