[
https://issues.jboss.org/browse/WFCORE-2615?page=com.atlassian.jira.plugi...
]
Ondrej Lukas updated WFCORE-2615:
---------------------------------
Description:
In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration
includes some SASL mechanisms then this attribute (and mechanisms configured there) is not
taken into account during choosing SASL mechanism. It means that client tries to use all
of mechanisms allowed on server side even if client does not allow them. e.g. in case when
server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it
tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms.
See log from wireshark in attachments. This is log for server configured through
"Steps to Reproduce".
This happens also for using allow-sasl-mechanisms from wildfly config and also for
programatically configured client.
We request blocker since it allows to use some SASL mechanisms even if they are not
allowed on client side.
was:
In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration
includes some SASL mechanisms then this attribute (and mechanisms configured there) is not
taken into account during choosing SASL mechanism. It means that client tries to use all
of mechanisms allowed on server side even if client does not allow them. e.g. in case when
server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it
tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms.
See log from wireshark in attachments. This is log for server configured through
"Steps to Reproduce".
This happens also for using allow-sasl-mechanisms from wildfly config and also for
programatically configured client.
We request blocker since this issue blocks RFE EAP7-567 and EAP7-568 and it allows to use
some SASL mechanisms even if they are not allowed on client side.
Attribute allow-sasl-mechanisms is ignored in Elytron Authentication
Configuration
----------------------------------------------------------------------------------
Key: WFCORE-2615
URL:
https://issues.jboss.org/browse/WFCORE-2615
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.0.Beta10
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
Attachments: dep.war, wireshark.pcapng
In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration
includes some SASL mechanisms then this attribute (and mechanisms configured there) is not
taken into account during choosing SASL mechanism. It means that client tries to use all
of mechanisms allowed on server side even if client does not allow them. e.g. in case when
server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it
tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms.
See log from wireshark in attachments. This is log for server configured through
"Steps to Reproduce".
This happens also for using allow-sasl-mechanisms from wildfly config and also for
programatically configured client.
We request blocker since it allows to use some SASL mechanisms even if they are not
allowed on client side.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)