【问题标题】:Ejabberd AuthenticationEjabberd 身份验证
【发布时间】:2018-12-21 17:10:59
【问题描述】:

我有我的 rails 应用程序。每当用户注册时,我也想在 ejabberd 节点上注册用户。但是,每当我使用 curl 请求调用注册 API 时,都会出现以下错误: {"status":"error","code":32,"message":"AccessRules: Account does not have the right to perform the operation."}

我的 curl 请求是:

curl -X POST --data '{"user": "bob", "host": "localhost", "password": "password"}' http://localhost:5443/api/register

我的ejabberd.yml文件如下:

hosts:
  - "localhost"

loglevel: 5
log_rotate_size: 10485760
log_rotate_date: ""
log_rotate_count: 1
log_rate_limit: 100

certfiles:
  - "/etc/letsencrypt/live/localhost/fullchain.pem"
  - "/etc/letsencrypt/live/localhost/privkey.pem"

listen:
  -
    port: 5222
    ip: "::"
    module: ejabberd_c2s
    max_stanza_size: 262144
    shaper: c2s_shaper
    access: c2s
    starttls_required: false
  -
    port: 5269
    ip: "::"
    module: ejabberd_s2s_in
    max_stanza_size: 524288
  -
    port: 5443
    ip: "0.0.0.0"
    module: ejabberd_http
    request_handlers:
      "/api": mod_http_api
      "/bosh": mod_bosh
      "/upload": mod_http_upload
      "/ws": ejabberd_http_ws
      "/oauth": ejabberd_oauth
    web_admin: true
    captcha: true
    tls: false

commands_admin_access: configure
commands:
  - add_commands: [user, admin, open]
oauth_expire: 3600
oauth_access: all


s2s_use_starttls: optional

acl:
  admin:
    user:
     - "admin@localhost"
  local:
    user_regexp: ""
  loopback:
    ip:
      - "127.0.0.0/8"
      - "::1/128"
      - "::FFFF:127.0.0.1/128"

access_rules:
  local:
    - allow: local
  c2s:
    - deny: blocked
    - allow
  announce:
    - allow: admin
  configure:
    - allow: admin
  muc_create:
    - allow: local
  pubsub_createnode:
    - allow: local
  register:
    - allow
  trusted_network:
    - allow: loopback
  oauth:
    - scope: "ejabberd:admin"
    - allow: admin

api_permissions:
  "console commands":
    from:
      - ejabberd_ctl
    who: all
    what: "*"
  "admin access":
    who:
      - access:
          - allow:
            - acl: admin@localhost
      - oauth:
        - scope: "ejabberd:admin"
        - access:
          - allow:
            - acl: admin@localhost
    what:
      - "*"
      - "!stop"
      - "!start"
  "public commands":
    who:
      - ip: "0.0.0.0"
    what:
      - "register"
      - "status"
      - "connected_users_number"

shaper:
  normal: 1000
  fast: 50000

shaper_rules:
  max_user_sessions: 10
  max_user_offline_messages:
    - 5000: admin
    - 100
  c2s_shaper:
    - none: admin
    - normal
  s2s_shaper: fast

modules:
  mod_adhoc: {}
  mod_admin_extra: {}
  mod_announce:
    access: announce
  mod_avatar: {}
  mod_blocking: {}
  mod_bosh: {}
  mod_caps: {}
  mod_carboncopy: {}
  mod_client_state: {}
  mod_configure: {}
  mod_disco: {}
  mod_fail2ban: {}
  mod_http_api: {}
  mod_http_upload:
    put_url: "https://@HOST@:5443/upload"
  mod_last: {}
  mod_mam:
    ## Mnesia is limited to 2GB, better to use an SQL backend
    ## For small servers SQLite is a good fit and is very easy
    ## to configure. Uncomment this when you have SQL configured:
    ## db_type: sql
    assume_mam_usage: true
    default: always
  mod_muc:
    access:
      - allow
    access_admin:
      - allow: admin
    access_create: muc_create
    access_persistent: muc_create
    default_room_options:
      mam: true
  mod_muc_admin: {}
  mod_offline:
    access_max_user_messages: max_user_offline_messages
  mod_ping: {}
  mod_privacy: {}
  mod_private: {}
  mod_proxy65:
    ip: "localhost"
    access: local
    max_connections: 5
  mod_pubsub:
    access_createnode: pubsub_createnode
    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
  mod_push: {}
  mod_push_keepalive: {}
  mod_register:
    ## Only accept registration requests from the "trusted"
    ## network (see access_rules section above).
    ## Think twice before enabling registration from any
    ## address. See the Jabber SPAM Manifesto for details:
    ## https://github.com/ge0rg/jabber-spam-fighting-manifesto
    ip_access: trusted_network
  mod_roster:
    versioning: true
  mod_s2s_dialback: {}
  mod_shared_roster: {}
  mod_stream_mgmt:
    resend_on_timeout: if_offline
  mod_vcard: {}
  mod_vcard_xupdate: {}
  mod_version:
  show_os: false

谁能指出我到底哪里错了?

提前致谢。

【问题讨论】:

    标签: ejabberd ejabberd-api ejabberd-auth


    【解决方案1】:

    如果你想使用 localhost 的 mod_http_api 来注册账号,你可以这样授予权限:

    api_permissions:
      "http_api commands":
        who:
          - ip: "127.0.0.1"
        from:
          - mod_http_api
        what:
          - "register"
    

    https://docs.ejabberd.im/developer/ejabberd-api/permissions/

    【讨论】:

      【解决方案2】:

      您在请求此之前是否已登录?还是您使用任何类型的身份验证机制? 如果你在没有这个的情况下请求尝试添加你请求 insode 的 ip

      "public commands":
          who:
            - ip: "0.0.0.0"
          what:
            - "register"
            - "status"
            - "connected_users_number"
      

      部分。 否则尝试在 api_permission 部分

      中添加 allow all under register

      【讨论】:

      • 是的,添加 ip 解决了问题。但我相信如果我将 ip 设置为 0.0.0.0,它应该接受来自所有 IP 地址的请求。但不确定为什么它会失败并给我错误..
      • 0.0.0.0 表示本地机器上的所有 IPv4 地址。您可能从外部 IP 地址请求
      • 这可能会导致潜在的安全问题,因为 0.0.0.0 意味着您正在绑定所有网络接口,包括可能暴露于公共互联网的接口。
      猜你喜欢
      • 2020-12-25
      • 2015-08-31
      • 2015-06-04
      • 1970-01-01
      • 1970-01-01
      • 2016-06-09
      • 1970-01-01
      • 2015-07-29
      • 2015-10-03
      相关资源
      最近更新 更多