Thank you for reporting this issue. Currently Tigase XMPP Server 7.2.0 is in intensive development phase and this issue is related to extensive changes in configuration of Tigase XMPP Server.

I've fixed issue with usage of custom SASL mechanisms, providers and callback handlers. As SASL settings are reused by JabberIqAuth processor, I created separate sasl-provider which will be used to configure SASL related settings.

In your case SASL configuration would look like this:

'sess-man' () {
    'sasl-provider' () {
        'mechanism-selector' (class: tigase.auth.CustomMechanismSelector) {}
        'callback-handler-factory' (class: tigase.auth.impl.ThirdAuthCallbackHandlerFactory) {}
        'customSaslServerFactory' (class: tigase.auth.mechanisms.CustomSaslServerFactory) {}
        'tigaseSaslServerFactory' (active: false) {}
    }
}

+Note:+ In my example I used @ tigase.auth.impl.ThirdAuthCallbackHandlerFactory@ which is implementation of @CallbackHandlerFactory@, so you need to implement callback handler factory - not only provide callback handler class, as in your example.

This fix will be part of a next snapshot build.

Thank you!

Can you give the ThirdAuthCallbackHandlerFactory code in here, let me reference it to write the implementation of CallbackHandlerFactory

As a reference for implementation of ThirdAuthCallbackHandlerFactory please use tigase.auth.CallbackHandlerFactory which is default callback handler for authentication mechanisms used by Tigase XMPP Server.

ok, thank you!