[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-4820:
-------------------------------------
Steps to Reproduce:
*Scenario One*
The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode.
{noformat}
<security-realm name="ldap_security_realm">
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
This results in the error: -
{noformat}
[Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
[Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
{noformat}
*Scenario Two*
A second scenario can be triggerd by defining the security realm as: -
{noformat}
<security-realm name="ldap_security_realm">
<server-identities>
<ssl>
<keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
</ssl>
</server-identities>
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
{noformat}
With the same outbound connection as in the first scenario.
The management-interfaces should be updated to: -
{noformat}
<management-interfaces>
<http-interface security-realm="ldap_security_realm">
<http-upgrade enabled="true"/>
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
{noformat}
This results in no clear error.
{noformat}
[Host Controller] 17:09:12,854 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{noformat}
was:
The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode.
{noformat}
<security-realm name="ldap_security_realm">
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
This results in the error: -
{noformat}
[Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
[Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
{noformat}
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-4820:
-------------------------------------
Steps to Reproduce:
The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode.
{noformat}
<security-realm name="ldap_security_realm">
<!--
<server-identities>
<ssl>
<keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
</ssl>
</server-identities>
-->
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
This results in the error: -
{noformat}
[Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
[Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
{noformat}
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-4820:
-------------------------------------
Steps to Reproduce:
The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode.
{noformat}
<security-realm name="ldap_security_realm">
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
This results in the error: -
{noformat}
[Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
[Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
{noformat}
was:
The minimal steps to reproduce are to add the following entries to the default host.xml and then start domain mode.
{noformat}
<security-realm name="ldap_security_realm">
<!--
<server-identities>
<ssl>
<keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
</ssl>
</server-identities>
-->
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
This results in the error: -
{noformat}
[Host Controller] 17:05:25,154 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.core.management.security.realm.ldap_security_realm: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.ldap_security_realm: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
[Host Controller] at org.jboss.as.domain.management.security.SecurityRealmService.start(SecurityRealmService.java:226)
[Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
{noformat}
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2441) Changes to MembershipListener, StateListener, MessageListener
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2441?page=com.atlassian.jira.plugin... ]
Bela Ban edited comment on JGRP-2441 at 1/30/20 11:37 AM:
----------------------------------------------------------
* Merged all {{X}} Listener interfaces into {{Receiver}}
* Removed {{ReceiverAdapter}} ({{Receiver}} has default methods)
* Removed {{suspect()}}: this method is only an indication that a member is suspected, and as such not very useful. The subsequent {{View}} is what counts.
was (Author: belaban):
* Merged all {{X}}Listener interfaces into {{Receiver}}
* Removed {{ReceiverAdapter}} ({{Receiver}} has default methods)
> Changes to MembershipListener,StateListener,MessageListener
> -----------------------------------------------------------
>
> Key: JGRP-2441
> URL: https://issues.redhat.com/browse/JGRP-2441
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0
>
>
> Investigate
> * Why is MessageListener still needed? Can't we just use {{Receiver}}?
> * Why does {{MessageListener}} subclass {{StateListener}}?
> * Are callbacks {{block()}}, {{unblock()}} and {{suspect()}} still needed?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-4820:
------------------------------------------
At the moment this does seem to be broken in WildFly 18 with the only workaround being migrating to an Elytron based configuration - presently looking at options for a fix in WildFly 19.
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Mark Sanchez (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Mark Sanchez commented on WFCORE-4820:
--------------------------------------
Any Status?
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4988) Test Scenario: improve DMN validation
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4988?page=com.atlassian.jira.plug... ]
Daniele Zonca updated DROOLS-4988:
----------------------------------
Description: Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too (was: Add a check to verify if a simple type has been changed to a complex type. Please consider expression columns too)
> Test Scenario: improve DMN validation
> -------------------------------------
>
> Key: DROOLS-4988
> URL: https://issues.redhat.com/browse/DROOLS-4988
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> Add a check to verify if a simple type has been changed to a structured type. Please consider expression columns too
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months