Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The documentation does not state information on permissions needed for the Elasticsearch user used to connect to Elasticsearch server #247

Closed
oussjarrousse opened this issue Sep 4, 2022 · 2 comments

Comments

@oussjarrousse
Copy link

While attempting to connect my zammad installation with an elasticsearch that I am hosting on another device. I created a special Elsaticsearch user for Zammad. I did not want to give too much permissions to the zammad ES user. However I did not find in the documentation the list of permissions required for a successful integration of EL and Zammad. https://docs.zammad.org/en/latest/install/elasticsearch.html

Eventually I ended up using the following solution:

Define a new EL role with the following permissions:

  • Cluster privileges: monitor, manage_ingest_pipelines
  • Index privileges:
    • indices: Zammad_*
    • privileges: create_index, create_doc, create, read

I think this info should be added to the documentation exactly here:
https://docs.zammad.org/en/latest/install/elasticsearch.html

@zerwes
Copy link

zerwes commented Jan 7, 2024

for me it is only working with the manage priv included.

zammad:
  cluster: [ "monitor", "manage_ingest_pipelines" ]
  indices:
    - names: [ 'Zammad_*', 'zammad_*' ]
      privileges: [ 'create_index', 'create_doc', 'create', 'read', 'manage' ]
  run_as: ["*"]

with

elasticsearch  8.11.3
zammad         6.2.0-1704392455.bba4f84a.bookworm 

But I fully agree that the required information should be provided in the documentation!

@ralf401
Copy link
Contributor

ralf401 commented Feb 18, 2025

Detailed ES config is out of scope of Zammad's documentation currently. We tend to link to the ES documentation for the configuration because it gets more and more complex to set it up. Maybe in the future we can add a detailed tutorial, but currently this is not planned.

I'll close this issue due to repo clean up reasons.

@ralf401 ralf401 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants