Andrzej Wójcik (Tigase) opened 2 years ago
-
This issue was reported by @bmalkow while working on channel bindings for Halcyon.
-
-
-
The issue was caused by during adding support for TLS 1.3, what caused refactoring and changing places when method notifying
SessionManagerabout connection encryption was called. I've added call for this method in places that should handle this forStartTLSand verified that with this change Tigase XMPP Server offers*-PLUSmechanisms forStartTLSandDirectTLSconnections. -
@bmalkow Please verify if this works as it should for you.
-
Bartosz Małkowski changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
Bartosz Małkowski added "Related" #1509 2 years ago
-
Wojciech Kapcia (Tigase) batch edited 1 year ago
Name Previous Value Current Value Iterations
empty tigase-server-8.4.0
-
Name Previous Value Current Value Version
8.4.0
tigase-server-8.4.0
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
tigase-server-8.4.0
|
| Server Version |
8.4.0
|
| Target Release |
1.0
|
| Sprints |
n/a
|
| Customer |
n/a
|
Iterations
-
tigase-server-8.4.0 Closed
Issue Votes (0)
Watchers (4)
We have enabled SCRAM *-PLUS mechanisms that will allow us to support Channel Binding. They work fine are available when DirectTLS connection is used, but they are unavailable when StartTLS connection is being used.