November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7459) (7.1.0) Upgrade Artemis to 1.5.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7459?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6828 to WFLY-7459: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7459 (was: JBEAP-6828) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) > (7.1.0) Upgrade Artemis to 1.5.0 > -------------------------------- > > Key: WFLY-7459 > URL: https://issues.jboss.org/browse/WFLY-7459 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7459) Upgrade Artemis to 1.5.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7459?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-7459: ------------------------------ Summary: Upgrade Artemis to 1.5.0 (was: (7.1.0) Upgrade Artemis to 1.5.0) > Upgrade Artemis to 1.5.0 > ------------------------ > > Key: WFLY-7459 > URL: https://issues.jboss.org/browse/WFLY-7459 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-711) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-711?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reopened ELY-711: ---------------------------- > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-711 > URL: https://issues.jboss.org/browse/ELY-711 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Choma > Assignee: Jan Kalina > > Basically Elytron clone of JBEAP-4114. > 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} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7458) EJB's async methods' Future#get should treat zero timeout as "don't wait"

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-7458: ----------------------------------- Summary: EJB's async methods' Future#get should treat zero timeout as "don't wait" Key: WFLY-7458 URL: https://issues.jboss.org/browse/WFLY-7458 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 8.2.0.Final Reporter: Ivo Studensky Assignee: Stuart Douglas Fix For: 10.1.0.CR1, 10.1.0.Final Say there is an asynchronous EJB method: {code} @Asynchronous public Future<Boolean> method() { ... } {code} Calling Future#get with a zero timeout: {code} if (bean.method().get(0, TimeUnit.MILLISECONDS)) {code} results in a block until the task is finished. Instead I expected zero waiting, because {{java.util.concurrent.Future.get(long, TimeUnit)}} doesn't specify any special treatment for a zero timeout value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-712) Elytron GSSCredential propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-712?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-712: --------------------------- Comment: was deleted (was: Tests green after ELY-693 resolving.) > Elytron GSSCredential propagation > --------------------------------- > > Key: ELY-712 > URL: https://issues.jboss.org/browse/ELY-712 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > User can't achieve identity propagation scenario with elytron, so far: > # Client authenticate to web application using SPNEGO > # Web application calls another service (database, another web application, ... ) on behalf of user. > # Web applications wants to use provided gss credential, but there is no way to get associated credentials in elytron, so far > Basically use case tested in AS TS with legacy security [1] > Legacy approach using {{DelegationCredentialContext.getDelegCredential()}} return null in elytron. > Actually there exists pull request the delegated credential will be associated with the SecurityIdentity [2] . This JIRA is created mainly for tracking purpose to process it properly once pending commit gets to EAP. > [1] https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testIdentityPropagation > [2] https://github.com/wildfly-security/wildfly-elytron/pull/434/commits/9b5a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7457) UT005013 causes OutOfMemoryError

by Steve Vater (JIRA)

Steve Vater created WFLY-7457: --------------------------------- Summary: UT005013 causes OutOfMemoryError Key: WFLY-7457 URL: https://issues.jboss.org/browse/WFLY-7457 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Steve Vater Assignee: Stuart Douglas There's some F5 WAF within the network where our WildFly is running. The WAF sends multiple Keep Alive-Requests to our WAF via TCP, but without sending "close_notify" after the communication has ended. Undertow throws UT005013, which is correct, but this causes the JVM to run out of Memory. The keepalive is sent 12 times per minute (every 5 seconds) to our WildFly. We already installed an update of Undertow (1.4.3); This didn't help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-712) Elytron GSSCredential propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-712?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reopened ELY-712: ---------------------------- > Elytron GSSCredential propagation > --------------------------------- > > Key: ELY-712 > URL: https://issues.jboss.org/browse/ELY-712 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > User can't achieve identity propagation scenario with elytron, so far: > # Client authenticate to web application using SPNEGO > # Web application calls another service (database, another web application, ... ) on behalf of user. > # Web applications wants to use provided gss credential, but there is no way to get associated credentials in elytron, so far > Basically use case tested in AS TS with legacy security [1] > Legacy approach using {{DelegationCredentialContext.getDelegCredential()}} return null in elytron. > Actually there exists pull request the delegated credential will be associated with the SecurityIdentity [2] . This JIRA is created mainly for tracking purpose to process it properly once pending commit gets to EAP. > [1] https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testIdentityPropagation > [2] https://github.com/wildfly-security/wildfly-elytron/pull/434/commits/9b5a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-712) Elytron GSSCredential propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-712?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-712: -------------------------------- Tests green after ELY-693 resolving. > Elytron GSSCredential propagation > --------------------------------- > > Key: ELY-712 > URL: https://issues.jboss.org/browse/ELY-712 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > User can't achieve identity propagation scenario with elytron, so far: > # Client authenticate to web application using SPNEGO > # Web application calls another service (database, another web application, ... ) on behalf of user. > # Web applications wants to use provided gss credential, but there is no way to get associated credentials in elytron, so far > Basically use case tested in AS TS with legacy security [1] > Legacy approach using {{DelegationCredentialContext.getDelegCredential()}} return null in elytron. > Actually there exists pull request the delegated credential will be associated with the SecurityIdentity [2] . This JIRA is created mainly for tracking purpose to process it properly once pending commit gets to EAP. > [1] https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testIdentityPropagation > [2] https://github.com/wildfly-security/wildfly-elytron/pull/434/commits/9b5a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-712) Elytron GSSCredential propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-712?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-712: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/534 > Elytron GSSCredential propagation > --------------------------------- > > Key: ELY-712 > URL: https://issues.jboss.org/browse/ELY-712 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > User can't achieve identity propagation scenario with elytron, so far: > # Client authenticate to web application using SPNEGO > # Web application calls another service (database, another web application, ... ) on behalf of user. > # Web applications wants to use provided gss credential, but there is no way to get associated credentials in elytron, so far > Basically use case tested in AS TS with legacy security [1] > Legacy approach using {{DelegationCredentialContext.getDelegCredential()}} return null in elytron. > Actually there exists pull request the delegated credential will be associated with the SecurityIdentity [2] . This JIRA is created mainly for tracking purpose to process it properly once pending commit gets to EAP. > [1] https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testIdentityPropagation > [2] https://github.com/wildfly-security/wildfly-elytron/pull/434/commits/9b5a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-712) Elytron GSSCredential propagation

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-712?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved JBEAP-6822 to ELY-712: --------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-712 (was: JBEAP-6822) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Authentication Mechanisms (was: Security) Affects Version/s: (was: 7.1.0.DR7) > Elytron GSSCredential propagation > --------------------------------- > > Key: ELY-712 > URL: https://issues.jboss.org/browse/ELY-712 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > User can't achieve identity propagation scenario with elytron, so far: > # Client authenticate to web application using SPNEGO > # Web application calls another service (database, another web application, ... ) on behalf of user. > # Web applications wants to use provided gss credential, but there is no way to get associated credentials in elytron, so far > Basically use case tested in AS TS with legacy security [1] > Legacy approach using {{DelegationCredentialContext.getDelegCredential()}} return null in elytron. > Actually there exists pull request the delegated credential will be associated with the SecurityIdentity [2] . This JIRA is created mainly for tracking purpose to process it properly once pending commit gets to EAP. > [1] https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testIdentityPropagation > [2] https://github.com/wildfly-security/wildfly-elytron/pull/434/commits/9b5a... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2016