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

roster_groups_allowed in .yml file doesn't accept list #3302

Open
relbraun opened this issue Jun 15, 2020 · 1 comment
Open

roster_groups_allowed in .yml file doesn't accept list #3302

relbraun opened this issue Jun 15, 2020 · 1 comment

Comments

@relbraun
Copy link

mod_pubsub:
    access_createnode: pubsub_createnode
    ## reduces resource comsumption, but XEP incompliant
    ignore_pep_from_offline: true
    ## XEP compliant, but increases resource comsumption
    ## ignore_pep_from_offline: false
    last_item_cache: false
    max_items_node: 1000
    plugins:
      - "flat"
      - "pep"
    force_node_config:
      ## Change from "whitelist" to "open" to enable OMEMO support
      ## See https://github.com/processone/ejabberd/issues/2425
      "eu.siacs.conversations.axolotl.*":
        access_model: whitelist
      ## Avoid buggy clients to make their bookmarks public
      "storage:bookmarks":
        access_model: whitelist
      "my:pep:x":
        access_model: roster
        notification_type: normal
        roster_groups_allowed: 
            - "group1"
            - "group2"

this config is not acceptable because roster_groups_allowed parameter expect string and not list. Any idea?

@prefiks
Copy link
Member

prefiks commented Jun 15, 2020

Indeed validator only accepts singular value here, so with current version you can't really do that - it requires changing validator to accept those. I will work on this.

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

3 participants