]
Jan Kalina updated WFLY-7349:
-----------------------------
Attachment: sasl-test.xml
SaslTestCase.java
configurable-sasl-server-factory cannot set mechanism information
-----------------------------------------------------------------
Key: WFLY-7349
URL:
https://issues.jboss.org/browse/WFLY-7349
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Jan Kalina
Assignee: Jan Kalina
Attachments: sasl-test.xml, SaslTestCase.java
sasl-authentication-factory and sasl-server-factory creates chain of SaslServerFactories
- for example ServerNameSaslServerFactory only delegates creating to following with
rewriting of the server name.
In this chain is also *SetMechanismInformationSaslServerFactory*, which only call
callback handler to send MechanismInformation into ServerAuthenticationContext - there it
will cause state change from InactiveState to InitialState.
The problem is, if the configurable-sasl-server-factory is used, the
*SetMechanismInformationSaslServerFactory* is in chain twice. The first occurence (by
sasl-authentication-factory) will cause change state to InitialState, but before the
serverName+protocol is overriden by SaslServerFactories following in chain. The second
occurence (by configurable-sasl-server-factory) already have serverName+protocol set, but
because the ServerAuthenticationContext is already in InitialState, the exception
"Too late to set" is thrown and createSaslServer returns null - fail
completely.
The chain of SaslServerFactories:
{code:java}
AuthenticationTimeoutSSF
TrustManagerSSF
AuthenticationCompleteSSF
SetMechanismInformationSSF => cbh => InactiveState -> InitialState(undefined,
null)
ServerNameSSF
ProtocolSSF
SetMechanismInformationSSF => cbh => "Too late to set" => return null
SecurityProviderSSF
{code}