tigase AuthRepository(digest plain otherAuth)-优快云博客

本文详细解析了Tigase XMPP Server中关于authentication的实现方式，特别是tigaseAuthRepository接口下的digestAuth、plainAuth和其他Auth三个接口的使用说明与区别。文章深入探讨了这些接口在不同版本中的变化，以及为何最终决定采用otherAuth接口来统一处理所有认证请求，以简化代码维护、简化API并方便扩展自定义认证协议。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

为什么80%的码农都做不了架构师？>>>

最近想自定下tigase的authentication，一直纠结

tigase AuthRepository接口digestAuth plainAuth otherAuth 3个接口的使用说明；

发现调试一直走的是otherAuth,再纠结其他的要不实现；最终找到2处说明；

1.http://www.tigase.org/content/sasl-custom-mechanisms-and-configuration

说的含糊；

GENERAL REMARKS
JabberIqAuth used for non-SASL authentication mechanisms uses the same callback as the SASL mechanisms.

Methods '*auth*' in '*Repository' interfaces will be deprecated. These interfaces will be treated as user details providers only. There will be new methods available which will allow for additional login operations on the database such as last successful login recording and so on….

最终在5.1的release说明里，找到了说法；全部走otherAuth,其他2个以备抛弃

http://www.tigase.org/content/tigase-xmpp-server-510-beta-3

Code refactored and deprecated methods for digestAuth and plainAuth. They are being replaced with otherAuth which handles now all authentication requests. This is to make the code simpler to maintain, simplify the API and make it easier to extend authentication protocols with custom ones.

转载于:https://my.oschina.net/greki/blog/213490