December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7747) Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7747?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-7747: ----------------------------- Component/s: Test Suite > Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7747 > URL: https://issues.jboss.org/browse/WFLY-7747 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > > The upgrade to JBoss Marshalling 2.0.0.Beta3 results in testsuite failures in {{org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase}} since Infinispan is still on JBoss Marshalling 1.4.x. Going to temporarily ignore these tests until we've upgraded to a version of Infinispan that depends on JBoss Marshalling 2.0.0.Beta3 (see WFLY-7746). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7747) Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7747?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-7747: ----------------------------- Labels: affects_elytron (was: ) > Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7747 > URL: https://issues.jboss.org/browse/WFLY-7747 > Project: WildFly > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > > The upgrade to JBoss Marshalling 2.0.0.Beta3 results in testsuite failures in {{org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase}} since Infinispan is still on JBoss Marshalling 1.4.x. Going to temporarily ignore these tests until we've upgraded to a version of Infinispan that depends on JBoss Marshalling 2.0.0.Beta3 (see WFLY-7746). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7766) Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved

by Farah Juma (JIRA)

Farah Juma created WFLY-7766: -------------------------------- Summary: Unignore org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase once WFLY-7746 is resolved Key: WFLY-7766 URL: https://issues.jboss.org/browse/WFLY-7766 Project: WildFly Issue Type: Bug Reporter: Farah Juma Assignee: Farah Juma The upgrade to JBoss Marshalling 2.0.0.Beta3 results in testsuite failures in {{org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase}} since Infinispan is still on JBoss Marshalling 1.4.x. Going to temporarily ignore these tests until we've upgraded to a version of Infinispan that depends on JBoss Marshalling 2.0.0.Beta3 (see WFLY-7746). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7765) Application deployed as "singleton-deployment" in a cluster is not reachable for EJB calls under all circumstances

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-7765: -------------------------------------- Summary: Application deployed as "singleton-deployment" in a cluster is not reachable for EJB calls under all circumstances Key: WFLY-7765 URL: https://issues.jboss.org/browse/WFLY-7765 Project: WildFly Issue Type: Bug Components: EJB Reporter: Wolf-Dieter Fink If an application (singleton-deployment) is deployed into a cluster with more nodes than are initial in the list of the client it can happen that a node is elected to run this application which is not know initially by the client, or the node with the singleton application is shutted down or crash during runtime. In any case the EJB invocation will not work if a node is elected to run the deployment which is not part of the servers listed as initial connections at client side. With some BYTEMAN rules I checked that the client side ClusterTopologyMessageHandler and ClusterNodeRemovalHandler did not see more than the node which have the application deployed. If all nodes are added to the client jboss-ejb-client.properties the DeploymentNodeSelector is used for the first invocation, the cluster-view is received with one node. After this node is down the DNS will show another node and the cluster-view received afterwards onyl show this node. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2098) Upgrade to Elytron Web 1.0.0.Beta6

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2098: ---------------------------------------- Summary: Upgrade to Elytron Web 1.0.0.Beta6 Key: WFCORE-2098 URL: https://issues.jboss.org/browse/WFCORE-2098 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha15 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2097) Upgrade to WildFly Elytron 1.1.0.Beta17

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2097: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta17 Key: WFCORE-2097 URL: https://issues.jboss.org/browse/WFCORE-2097 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha15 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-824) Release WildFly Elytron 1.1.0.Beta17

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-824: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta17 Key: ELY-824 URL: https://issues.jboss.org/browse/ELY-824 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta17 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2096) ServiceTarget and ServiceBuilder provided by OperationContext remain coupled to the context after the op is complete

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2096: ---------------------------------------- Summary: ServiceTarget and ServiceBuilder provided by OperationContext remain coupled to the context after the op is complete Key: WFCORE-2096 URL: https://issues.jboss.org/browse/WFCORE-2096 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry OperationContextImpl provides impls of ServiceTarget and ServiceBuilder to OSHs. It is valid for those OSHs to pass those (particularly the ServiceTarget) out to other code, e.g. DUPs, which will then use them as a kind of "subsystem scoped" target. (As opposed, say, to a deployment scoped target that can be obtained from the DeploymentUnitService. If this is done though, the target and builders continue to a ref to the state held by the OperationContext that created them. That state is no longer relevant once the management op is done and retaining a ref to it is a kind of memory leak. Any link back to the OC should be cleared from these objecdts when the operation is complete. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7322) LDAP referrals does not work in Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7322?page=com.atlassian.jira.plugin.... ] Jan Kalina resolved WFLY-7322. ------------------------------ Resolution: Done > LDAP referrals does not work in Elytron ldap-realm > -------------------------------------------------- > > Key: WFLY-7322 > URL: https://issues.jboss.org/browse/WFLY-7322 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > LDAP referrals cannot be used in Elytron {{ldap-realm}}. Ldap Realm is currently not prepared to work with referrals at all: > * {{ldap-realm}} does not include any options which enable working with LDAP referrals (PicketBox use {{baseFilter}} option which can be configured to return also referral object) > * implementation of {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm}} does not include any logic which handles referrals > Referrals are important feature of LDAP. It has to be covered by Elytron => requested blocker flag. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7764) Enable Elytron JACC Integration

by Pedro Igor (JIRA)

Pedro Igor created WFLY-7764: -------------------------------- Summary: Enable Elytron JACC Integration Key: WFLY-7764 URL: https://issues.jboss.org/browse/WFLY-7764 Project: WildFly Issue Type: Enhancement Components: Security Reporter: Pedro Igor Assignee: Pedro Igor Enable Elytron JACC integration for both WEB and EJB subsystems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 7 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 December 2016