August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-261: --------------------------------- Fix Version/s: 1.1.0.CR7 (was: 1.1.0.CR6) > Rework (and move) UsernamePasswordHashUtil > ------------------------------------------ > > Key: ELY-261 > URL: https://issues.jboss.org/browse/ELY-261 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI, Passwords > Reporter: Darran Lofthouse > Fix For: 1.1.0.CR7 > > > Firstly this class is not really SASL specific so should be in a general util package. > Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1335) In a continuation required situation create the scope if it doesn't already exist

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1335?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1335: ---------------------------------- Fix Version/s: 1.1.0.CR7 (was: 1.1.0.CR6) > In a continuation required situation create the scope if it doesn't already exist > --------------------------------------------------------------------------------- > > Key: ELY-1335 > URL: https://issues.jboss.org/browse/ELY-1335 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR7 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1334) Release WildFly Elytron 1.1.0.CR6

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1334?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1334: ---------------------------------- Fix Version/s: 1.1.0.CR7 (was: 1.1.0.CR6) > Release WildFly Elytron 1.1.0.CR6 > --------------------------------- > > Key: ELY-1334 > URL: https://issues.jboss.org/browse/ELY-1334 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.CR7 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1309) Channel binding callback cannot support tls-unique

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1309?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1309: ---------------------------------- Fix Version/s: 1.1.0.CR7 (was: 1.1.0.CR6) > Channel binding callback cannot support tls-unique > -------------------------------------------------- > > Key: ELY-1309 > URL: https://issues.jboss.org/browse/ELY-1309 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI, Authentication Client, Authentication Server, Callbacks, SASL > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Blocker > Fix For: 1.1.0.CR7 > > > The revised API for the channel binding callback uses SSL sessions, but the standard TLS channel binding types [according to the RFC|https://tools.ietf.org/html/rfc5929] are associated with the connection, not the session. It is likely that the proposed channel bindings JDK API will exist on SSLSocket/SSLEngine. Introduce an API that allows the callback handlers to acquire the connection information using a forward-compatible API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1335) In a continuation required situation create the scope if it doesn't already exist

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1335: ------------------------------------- Summary: In a continuation required situation create the scope if it doesn't already exist Key: ELY-1335 URL: https://issues.jboss.org/browse/ELY-1335 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.1.0.CR6 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9237) Remarshaling the default configuration xml files shouldn't change the files

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFLY-9237: --------------------------------------- Summary: Remarshaling the default configuration xml files shouldn't change the files Key: WFLY-9237 URL: https://issues.jboss.org/browse/WFLY-9237 Project: WildFly Issue Type: Enhancement Components: Domain Management Affects Versions: 11.0.0.Beta1 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Starting a server and provoking a marshaling of the model without any real change on the default configuration files shouldn't result in a different files (with empty lines). Reproducer: * start the server or domain * add and remove a system property using the CLI * diff the resulting configuration file with the initial one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9235) @Resource injection does not fail in a servlet when the resource is missing

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9235?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9235: --------------------------------- Assignee: Stuart Douglas (was: Jason Greene) > @Resource injection does not fail in a servlet when the resource is missing > --------------------------------------------------------------------------- > > Key: WFLY-9235 > URL: https://issues.jboss.org/browse/WFLY-9235 > Project: WildFly > Issue Type: Bug > Components: Naming, Web (Undertow) > Reporter: Stephen Coy > Assignee: Stuart Douglas > Attachments: web45709634.jira.zip > > > The attached web application builds, deploys and runs perfectly. > However, if you remove one of the <env-entry> elements from the web.xml it will still deploy and run. > The associated injection point is left as null instead of having the deployment fail as required by the Java EE 7 Spec in "EE.5.2.5 Annotations and Injection", where it states: > {quote} If the container fails to find a resource needed for injection, initialization of the class must fail, and the class must not be put into service.{quote} > Also see StackOverflow question https://stackoverflow.com/questions/45716813/glassfish-wildfly-not-failin... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9236) Remarshaling the default configuration xml files shouldn't change the files

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-9236?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet moved WFCORE-3194 to WFLY-9236: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-9236 (was: WFCORE-3194) Component/s: Domain Management (was: Domain Management) Affects Version/s: 11.0.0.Beta1 (was: 3.0.0.Beta31) > Remarshaling the default configuration xml files shouldn't change the files > --------------------------------------------------------------------------- > > Key: WFLY-9236 > URL: https://issues.jboss.org/browse/WFLY-9236 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 11.0.0.Beta1 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Starting a server and provoking a marshaling of the model without any real change on the default configuration files shouldn't result in a different files (with empty lines). > Reproducer: > * start the server or domain > * add and remove a system property using the CLI > * diff the resulting configuration file with the initial one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3158) Upgrade to xnio 3.5.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3158?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFCORE-3158: ------------------------------------ https://github.com/xnio/xnio/pull/127 contains the upgrades since I don't have push rights to xnio. I am renaming this to 3.5.1.Final since I forgot to upgrade a few things in the pom for the 3.5.0.Final release. > Upgrade to xnio 3.5.0.Final > --------------------------- > > Key: WFCORE-3158 > URL: https://issues.jboss.org/browse/WFCORE-3158 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3158) Upgrade to xnio 3.5.1.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3158?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-3158: ------------------------------- Summary: Upgrade to xnio 3.5.1.Final (was: Upgrade to xnio 3.5.0.Final) > Upgrade to xnio 3.5.1.Final > --------------------------- > > Key: WFCORE-3158 > URL: https://issues.jboss.org/browse/WFCORE-3158 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 August 2017