Versions Compared

Old Version 8

changes.mady.by.user Simone Conrad

Saved on

compared with

New Version Current

changes.mady.by.user Simone Conrad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
<repoName>.protocolservice.type=elasticv2
<repoName>.protocolservice.elasticv2.host = http://127.0.0.1:9200
<repoName>.protocolservice.elasticv2.index.create = protocol-fi
<repoName>.protocolservice.elasticv2.index.read = protocol-fi
<repoName>.protocolservice.elasticv2.index.update = protocol-fi
<repoName>.protocolservice.elasticv2.index.delete = protocol-fi
<repoName>.protocolservice.elasticv2.index.info = protocol-fi
<repoName>.protocolservice.elasticv2.index.admin = protocol-fi
<repoName>.protocolservice.elasticv2.index.unknown = protocol-fi
#<repoName>.protocolservice.elasticv2.authentication.type= #default: none
#<repoName>.protocolservice.elasticv2.authentication.credentials= #default:
#<repoName>.protocolservice.elasticv2.maxconnections= #default: 50
#<repoName>.protocolservice.elasticv2.connecttimeout= #default: 5
#<repoName>.protocolservice.elasticv2.sockettimeout= #default: 30
#<repoName>.protocolservice.elasticv2.requesttimeout= #default: 10
#<repoName>.protocolservice.elasticv2.fallback.type= #default:
Info

Notes for Elastic 8

Starting with version 8. By default when starting the Elastic server Security and HTTPS is enabled. This may be useful, but for local testing it’s rather a hindrance.
It can be deactivated by editing the file: config/elasticsearch.yml, adding the following entries:

Code Block
xpack.security.enabled: false
xpack.security.transport.ssl.enabled: false
xpack.security.http.ssl.enabled: false

(QuelleSource citation: https://discuss.elastic.co/t/cannot-disable-security-in-8-1/299857 )