Projects tigase _server server-core Issues #1403
xmpp-sasl setting doesn't work (#1403)
Unknown opened 5 years ago
 'urn:ietf:params:xml:ns:xmpp-sasl' () {
     'callbackhandler-PLAIN'='com.eliao.tigase.RedisCallbackHandler'
}
  • Unknown commented 5 years ago

    This processor works as expected. Please check documentation for usage of custom SASL callback handlers as your configuration is invalid, see https://docs.tigase.net/tigase-server/8.1.0/Development_Guide/html/#saslcmac

  • Unknown commented 5 years ago

    Here is my configuration,nothing else。What's wrong

    'sess-man' (class: com.demo.tigase.DemoSessionManager) {
        'urn:ietf:params:xml:ns:xmpp-sasl' () {
            'callbackhandler' = 'com.demo.tigase.RedisCallbackHandler'
         }
    }
    
  • Unknown commented 5 years ago

    I use version 8.0

  • Unknown commented 5 years ago

    Could you explain what does it mean "doesn't work"? Does it generates errors/exceptions? Or the expected result differ?

    Please also explain what are you trying to achieve.

    Btw. We recently released 8.1.0 (https://github.com/tigase/tigase-server/releases/tag/tigase-server-8.1.0) and it's recommendable to use this version.

  • Unknown commented 5 years ago

    thank you!It's ok now

  • Unknown commented 5 years ago

    There are the following content in the config.tdsl file

    'sess-man' (class: com.demo.tigase.DemoSessionManager) {
        'urn:ietf:params:xml:ns:xmpp-sasl' () {
            'callbackhandler' = 'com.demo.tigase.RedisCallbackHandler'
         }
    }
    

    but in ‘config-dump.properties’ file ,There is no information about ‘com.demo.tigase.RedisCallbackHandler’,This is OK in 7.1.3。

     'urn:ietf:params:xml:ns:xmpp-sasl' (class: tigase.xmpp.impl.SaslAuth) {
            queueSize = null
            threadsNo = 32
    }
    

    also RedisCallbackHandler is not running.

    That's what I said "doesn't work"

    It was solved in other ways

issue 1 of 1
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#1403
Please wait...
Page is in error, reload to recover