March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10065) Clustering TS: change deployment/module names to test class names

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-10065: ------------------------------------- Summary: Clustering TS: change deployment/module names to test class names Key: WFLY-10065 URL: https://issues.jboss.org/browse/WFLY-10065 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 12.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor This makes debugging in large logs much faster, since deployments can be associated with test cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1468) IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1468?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1468: ---------------------------- Labels: ibm-java (was: ) > IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported > --------------------------------------------------------------------------- > > Key: ELY-1468 > URL: https://issues.jboss.org/browse/ELY-1468 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Beta10 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Minor > Labels: ibm-java > > When more mechanismTypes is provided but the Kerberos mechanism is not listed as the supported one then authentication should fail. And 401 should be returned, but 403 is on IBM java. > This issue was hidden by ELY-1340. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1468) IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1468?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1468: ------------------------------- Assignee: Jan Kalina > IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported > --------------------------------------------------------------------------- > > Key: ELY-1468 > URL: https://issues.jboss.org/browse/ELY-1468 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Beta10 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Minor > > When more mechanismTypes is provided but the Kerberos mechanism is not listed as the supported one then authentication should fail. And 401 should be returned, but 403 is on IBM java. > This issue was hidden by ELY-1340. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-715) SPNEGO: missing negState field in the first reply for defective token

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-715?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-715 at 3/21/18 12:32 PM: ---------------------------------------------------------- Note: this issue cover "Defective token" (which cannot be parsed and gssContext throws GSSException), but not "Invalid token" (which is expired for example and gssContext returns srcName = null) - that is in ELY-1547 was (Author: honza889): Note: this issue cover "Defective token" (which cannot be parsed and gssContext throws GSSException), but not "Invalid token" (which is expired for example and gssContext returns srcName = null) > SPNEGO: missing negState field in the first reply for defective token > --------------------------------------------------------------------- > > Key: ELY-715 > URL: https://issues.jboss.org/browse/ELY-715 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Fix For: 1.1.0.CR2 > > > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10064) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10064?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10064: -------------------------------- Description: Ensure we set the eviction strategy to REMOVE or MANUAL based on the configured size. (was: Integrate MANUAL eviction strategy introduced in ISPN-6911.) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10064 > URL: https://issues.jboss.org/browse/WFLY-10064 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Ensure we set the eviction strategy to REMOVE or MANUAL based on the configured size. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10064) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-10064: ----------------------------------- Summary: Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." Key: WFLY-10064 URL: https://issues.jboss.org/browse/WFLY-10064 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10064) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10064?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10064: -------------------------------- Affects Version/s: 12.0.0.Final (was: 10.0.0.Final) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10064 > URL: https://issues.jboss.org/browse/WFLY-10064 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10064) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10064?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10064: -------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/9390) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10064 > URL: https://issues.jboss.org/browse/WFLY-10064 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10064) Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated."

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10064?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10064: -------------------------------- Fix Version/s: (was: 11.0.0.Alpha1) > Silence "ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated." > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-10064 > URL: https://issues.jboss.org/browse/WFLY-10064 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Integrate MANUAL eviction strategy introduced in ISPN-6911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2412) Fix handling of fireUntilHalt in 2 tests

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2412: ------------------------------------- Summary: Fix handling of fireUntilHalt in 2 tests Key: DROOLS-2412 URL: https://issues.jboss.org/browse/DROOLS-2412 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.6.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi IncrementalCompilationTest.testMultipleIncrementalCompilationsWithFireUntilHalt() and TimerAndCalendarTest.testHaltAfterSomeTimeThenRestartButNoLongerHolding() handle fireUntilHalt like that there could remain fireUntilHalt thread hanging. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018