[
https://issues.jboss.org/browse/WFCORE-3318?page=com.atlassian.jira.plugi...
]
David Lloyd commented on WFCORE-3318:
-------------------------------------
The correct way to configure the client-side realm would be to call "useRealm()"
method in the AuthenticationConfiguration. The property is not respected for this
purpose. Also in the WildFly case, the list of realms applies on the server, not the
client, and is configured in the mechanism configuration.
The class you reference is an adapter for legacy compatibility cases outside of the
server.
User is unable to use WildflySasl.REALM_LIST property together with
DIGEST-MD5
------------------------------------------------------------------------------
Key: WFCORE-3318
URL:
https://issues.jboss.org/browse/WFCORE-3318
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
User is unable to use WildflySasl.REALM_LIST property together with DIGEST-MD5.
When I look to org.wildfly.security.sasl.digest.DigestServerFactory [1] I see there
callback handler and I expect that this callback handle
org.wildfly.security.sasl.util.AvailableRealmsSaslServerFactory too. When you look into
this factory [2] you can see that there is processed property REALM_LIST.
I added there break point but nothing happened.
If I understand correctly I found out that in SaslServerDefinitions [3] is not added
AvailableRealmsSaslServerFactory when property (or some another condition) is set.
[1]
https://github.com/wildfly-security/wildfly-elytron/blob/1.2.0.Beta3/src/...
[2]
https://github.com/wildfly-security/wildfly-elytron/blob/1.2.0.Beta3/src/...
[3]
https://github.com/wildfly/wildfly-core/blob/3.0.3.Final/elytron/src/main...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)