November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11385) Referrals roles assignment for referral user does not work for AdvancedLdapLoginModule with Active Directory

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-11385?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-15888 to WFLY-11385: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11385 (was: JBEAP-15888) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: (was: 7.0.0.ER4) Fix Version/s: (was: 7.2.1.GA) > Referrals roles assignment for referral user does not work for AdvancedLdapLoginModule with Active Directory > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11385 > URL: https://issues.jboss.org/browse/WFLY-11385 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Tomas Hofman > Assignee: Jiri Ondrusek > Priority: Minor > > Consider two MS Active Directory domains with configured crossRef to each other. EAP using AdvancedLdapLoginModule for MS AD with referrals and rolesCtxDN is set to the referral DN where user account are stored; also EAP is configured for searching roles based on users entries (mapping users to roles). > If referral users (from EAP point of view - hostname is configured for original LDAP and user is obtained as referral user - from second of domains) authenticate then they have not assigned roles from AD attribute from 'roleAttributeID' option. > Example: > I have two MS AD domains - DC=jboss,DC=test (Domain A) and DC=jboss,DC=test2 (Domain B) with crossRef. > Part of ldif for Domain A: > {code} > ... > dn: CN=TheDuke,OU=Roles,O=eapqe,DC=jboss,DC=test > objectClass: groupOfNames > objectClass: top > cn: TheDuke > businessCategory: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > member: CN=jdukeNotUsed,OU=People,O=eapqe,DC=jboss,DC=test > ... > {code} > Part of ldif for Domain B > {code} > ... > dn: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > objectclass: top > objectclass: person > objectClass: inetOrgPerson > cn: jduke > sn: Duke > description: CN=TheDuke,OU=Roles,O=eapqe,DC=jboss,DC=test > description: CN=Admin,OU=Roles,O=eapqe,DC=jboss,DC=test2 > userPassword: Password1 > dn: CN=Admin,OU=Roles,O=eapqe,DC=jboss,DC=test2 > objectClass: groupOfNames > objectClass: top > cn: Admin > businessCategory: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > member: CN=jdukeNotUsed,OU=People,O=eapqe,DC=jboss,DC=test2 > ... > {code} > EAP AdvancedLdapLoginModule is configured: > {code:xml} > <security-domain name="AdvancedLdapReferrals"> > <authentication> > <login-module code="AdvancedLdap" flag="required"> > <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> > <module-option name="java.naming.provider.url" value="HOSTNAME_OF_DOMAIN_A"/> > <module-option name="bindDN" value="BIND_DN"/> > <module-option name="bindCredential" value="PASSWORD"/> > <module-option name="referralUserAttributeIDToCheck" value="businessCategory"/> > <module-option name="roleAttributeIsDN" value="true"/> > <module-option name="roleFilter" value="(CN={0})"/> > <module-option name="roleAttributeID" value="description"/> > <module-option name="rolesCtxDN" value="OU=People,O=eapqe,DC=jboss,DC=test2"/> > <module-option name="java.naming.security.authentication" value="simple"/> > <module-option name="baseCtxDN" value="OU=People,O=eapqe,DC=jboss,DC=test2"/> > <module-option name="java.naming.referral" value="follow"/> > <module-option name="throwValidateError" value="true"/> > <module-option name="baseFilter" value="(CN={0})"/> > <module-option name="roleNameAttributeID" value="CN"/> > </login-module> > </authentication> > </security-domain> > {code} > Then when jduke try to authenticate to application roles TheDuke and Admin should be assigned to him. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11384) StatefulFailoverTestCase fails intermittently

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-11384: ----------------------------------- Summary: StatefulFailoverTestCase fails intermittently Key: WFLY-11384 URL: https://issues.jboss.org/browse/WFLY-11384 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 15.0.0.Beta1 Environment: Any Reporter: Ondrej Kotek Assignee: Radoslav Husar The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example: {noformat} [ERROR] Failures: [ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3> {noformat} or {noformat} [ERROR] Failures: [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500> {noformat} Estimated failure rate is 50 %. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11143) Message sent to JMSReplyTo from old client does not find correct binding

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11143?page=com.atlassian.jira.plugin... ] Miroslav Novak reopened WFLY-11143: ----------------------------------- > Message sent to JMSReplyTo from old client does not find correct binding > ------------------------------------------------------------------------ > > Key: WFLY-11143 > URL: https://issues.jboss.org/browse/WFLY-11143 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Fix For: 15.0.0.CR1 > > > There is regression in backward compatibility of messaging client. JMSReplyTo destination set by older client contains incorrect address which causes that reply message does not have correct binding and such message is lost. > Impact: Applications will stop work after upgrade to WF14/EAP 7.2.0.CD14. > Test Scenario: > * Start EAP 7.2.0.CD14/WF14 server (Artemis 2.x) with deployed InQueue and OutQueue > * Send message to InQueue from older EAP 7.2.0.CD13/WF13/Artemis 1.5.5 client to InQueue. Message has JMSReplyTo header set to OutQueue. Client got "OutQueue" queue from JNDI lookup from EAP7.2.0.CD14/WF14 > * Deploy MDB to server > ** MDB consumes message from InQueue and sends new message to destination defined in JMSReplyTo header (so to OutQueue) > * Receive message from OutQueue > Result: > No message is received from OutQueue. There is debug message in server log: > {code} > 11:36:09,565 DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-25 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@22848193)) Message CoreMessage[m > essageID=214,durable=true,userID=c0de8bd0-cba6-11e8-840f-f496342f6705,priority=4, timestamp=Tue Oct 09 11:36:09 CEST 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=580,properties=TypedPropertie > s[inMessageId=ID:c0383a39-cba6-11e8-95ad-f496342f6705,__AMQ_CID=c0d9349a-cba6-11e8-840f-f496342f6705,_AMQ_DUPL_ID=90d1e80e-116d-4eef-9513-84c6085549db,_AMQ_ROUTING_TYPE=0]]@1680840457 is not going anywhere as it > didn't have a binding on address:jms.queue.OutQueue > {code} > which indicates that jms.queue.OutQueue address does not have a binding. > The same happesn if older EAP/WF server (with Artemis 1.5.5x) is used and new EAP 7.2.0.CD14/WF14(Artemis 2.x) client is used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

by Justin Bertram (Jira)

[ https://issues.jboss.org/browse/WFWIP-148?page=com.atlassian.jira.plugin.... ] Justin Bertram reassigned WFWIP-148: ------------------------------------ Assignee: Justin Bertram (was: Martyn Taylor) > Artemis logging codes/IDs have changed for CORE protocol > -------------------------------------------------------- > > Key: WFWIP-148 > URL: https://issues.jboss.org/browse/WFWIP-148 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 > For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > {code} > but newly it would have code AMQ219007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.] > {code} > This is problem for any user/customer who had monitoring based on those codes as this will require to change it. > The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3339?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-3339: ---------------------------------- Description: Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance. > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.jboss.org/browse/DROOLS-3339 > Project: Drools > Issue Type: Epic > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: michael mccune > Assignee: michael mccune > Priority: Critical > > Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the regression model to use an external library for regressions

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3339?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-3339: ---------------------------------- Component/s: PMML > refactor the regression model to use an external library for regressions > ------------------------------------------------------------------------ > > Key: DROOLS-3339 > URL: https://issues.jboss.org/browse/DROOLS-3339 > Project: Drools > Issue Type: Epic > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: michael mccune > Assignee: michael mccune > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by michael mccune (Jira)

[ https://issues.jboss.org/browse/DROOLS-3339?page=com.atlassian.jira.plugi... ] michael mccune updated DROOLS-3339: ----------------------------------- Summary: refactor the PMML regression model to use an external library for regressions (was: refactor the regression model to use an external library for regressions) > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.jboss.org/browse/DROOLS-3339 > Project: Drools > Issue Type: Epic > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: michael mccune > Assignee: michael mccune > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3339?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-3339: ---------------------------------- Affects Version/s: 7.14.0.Final > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.jboss.org/browse/DROOLS-3339 > Project: Drools > Issue Type: Epic > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: michael mccune > Assignee: michael mccune > Priority: Critical > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the regression model to use an external library for regressions

by michael mccune (Jira)

michael mccune created DROOLS-3339: -------------------------------------- Summary: refactor the regression model to use an external library for regressions Key: DROOLS-3339 URL: https://issues.jboss.org/browse/DROOLS-3339 Project: Drools Issue Type: Epic Reporter: michael mccune Assignee: michael mccune -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11374: ------------------------------- Attachment: slave-server-linux.log slave-server-windows.log master-server-linux.log master-server-windows.log > Master Artemis in Wildfly 10.0.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Reporter: Srinivas ev > Assignee: Jason Greene > Priority: Critical > Attachments: master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018