-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR19
I'm not able to get PLUS SASL mechanisms (i.e. the ones with channel binding) working. It seems there is a missing piece of integration. The mechanisms are required by EAP7-530 and EAP7-142.
I don't see the wrapper SASL factories, which are responsible for handling ChannelBindingCallback, used in the application server. (e.g. the TLSServerEndPointChannelBindingSaslClientFactory).
This issue is blocking test development.
There is still a chance the problem is in my test configuration, but the documentation of this topic is still a little bit sparse.
- is blocked by
-
JBEAP-11911 Upgrade JBoss Remoting to 5.0.0.CR4
- Closed
- is caused by
-
REM3-291 SSL information should be available on inner authentications
- Resolved
- is cloned by
-
ELY-1232 Elytron - SCRAM PLUS SASL mechanisms don't work - part of channel binding integration seems to be missing
- Resolved
- is incorporated by
-
JBEAP-11137 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta26
- Closed
-
JBEAP-11466 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta28
- Closed
- is related to
-
JBEAP-12231 Handle properly non-PLUS Elytron SASL mechanisms when SSL context is used (i.e. channel binding is possible)
- Closed
-
JBEAP-12689 Elytron GS2-KRB5 SASL mechanism (non-PLUS) is allowed even if the channel binding is possible
- Closed
- relates to
-
JBEAP-11925 Coverity static analysis: Dereference null return value in ServerAuthenticationContext (Elytron)
- Closed
-
JBEAP-12232 Document how are SASL mechanisms handled when they support channel binding
- Closed