Claus Weng opened 8 years ago
|
|
It looks like your custom authentication mechanism is not used and your XMPP client prefers to use SCRAM-SHA1 mechanism which is not working with your implementation of @AuthRepository@, ie. due to encoded passwords in a database, password not being stored in a database or similar issue. We are working on a mechanism which will disable SCRAM-SHA1 if it cannot be used but it will be available in version 7.2.0, see #4814 As I workaround for version 7.1.0 and 7.1.1, I would like to suggest to add following entry to
which will disable |
|
Thank you very much. sess-man/plugins-conf/enabled-mechanisms=PLAIN,DIGEST-MD5 did the trick |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
5457
|
Version |
tigase-server-7.1.1
|
Spent time |
2h 30m
|
Issue Votes (0)
Watchers (0)
Hi
We are currently running tigase 5.2.2 with a custom authentication. We are trying to upgrade our tigase server to 7.1.0 and we have implemented the methods in our custom auth according to the tigase.db.AuthRepository.
The server starts up fine as I can see (I've attached the console.log) but our clients cannot connect and in the log we only get:
java.lang.IllegalArgumentException: Empty key
I've attached the init.properties (removed sensitive info)
Looking forward to hear from you
Best regards
Claus Weng
init.properties tigase-console.log