June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8986) Duplicate licenses.xml files in the feature-pack module source tree

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-8986: -------------------------------------- Summary: Duplicate licenses.xml files in the feature-pack module source tree Key: WFLY-8986 URL: https://issues.jboss.org/browse/WFLY-8986 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The feature-pack module includes src/licenses/licenses.xml and src/main/resources/content/docs/licenses/licenses.xml. The build overwrites the latter with the former but the latter currently includes a dep not found in the latter. Task is to remove the latter and update the former with the missing dep. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8987) Duplicate licenses.xml files in the feature-pack module source tree

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-8987: -------------------------------------- Summary: Duplicate licenses.xml files in the feature-pack module source tree Key: WFLY-8987 URL: https://issues.jboss.org/browse/WFLY-8987 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The feature-pack module includes src/licenses/licenses.xml and src/main/resources/content/docs/licenses/licenses.xml. The build overwrites the latter with the former but the latter currently includes a dep not found in the latter. Task is to remove the latter and update the former with the missing dep. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2972) Upgrade WildFly Elytron to 1.1.0.Beta54

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2972?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2972: ------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.Beta54 (was: Upgrade WildFly Elytron to 1.1.0.Beta53) > Upgrade WildFly Elytron to 1.1.0.Beta54 > --------------------------------------- > > Key: WFCORE-2972 > URL: https://issues.jboss.org/browse/WFCORE-2972 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1067) Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1067?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1067: ---------------------------------- Fix Version/s: 1.1.0.Beta55 (was: 1.1.0.Beta54) > Add support to use default GSSCredential CredentalSource with AuthenticationConfiguration from XML > -------------------------------------------------------------------------------------------------- > > Key: ELY-1067 > URL: https://issues.jboss.org/browse/ELY-1067 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta55 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1031) Make the CredentialStore class final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1031?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1031: ---------------------------------- Fix Version/s: 1.1.0.Beta55 (was: 1.1.0.Beta54) > Make the CredentialStore class final > ------------------------------------ > > Key: ELY-1031 > URL: https://issues.jboss.org/browse/ELY-1031 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credential Store > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Priority: Critical > Fix For: 1.1.0.Beta55 > > > Unless there is a reason this has not already be done the class should probably be made final to be sure extension is not possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-715?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-715: --------------------------------- Fix Version/s: 1.1.0.Beta55 (was: 1.1.0.Beta54) > SPNEGO: missing negstat field in the first reply > ------------------------------------------------ > > 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.Beta55 > > > 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.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1170: ---------------------------------- Fix Version/s: 1.1.0.Beta55 (was: 1.1.0.Beta54) > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta55 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1114) Check for realm availability when selecting a DIGEST mechanism realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1114?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1114: ---------------------------------- Fix Version/s: 1.1.0.Beta55 (was: 1.1.0.Beta54) > Check for realm availability when selecting a DIGEST mechanism realm > -------------------------------------------------------------------- > > Key: ELY-1114 > URL: https://issues.jboss.org/browse/ELY-1114 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Affects Versions: 1.1.0.Beta39, 1.1.0.Beta44 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta41, 1.1.0.Beta55 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1260) Release WildFly Elytron 1.1.0.Beta54

by Darran Lofthouse (JIRA)

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

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2995) WildFly: support logback.xml in Per-deployment Logging (instead of silently ignoring logback.xml)

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2995?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-2995: ------------------------------------- bq. The problem is logback is a log manager as is the JBoss Log Manager. To get WildFly to work with log4j we forked log4j and replaced the log manager parts to delegate to the JBoss Log Manager. In order to get this to work log4j2 or logback we'd have to do the same type of thing. I agree. However it may still be worth doing, or at least researching a bit. > WildFly: support logback.xml in Per-deployment Logging (instead of silently ignoring logback.xml) > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-2995 > URL: https://issues.jboss.org/browse/WFCORE-2995 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: Geoffrey De Smet > Assignee: James Perkins > > Wildfly currently supports the following _Per deployment logging_ configurations [1]: > logging.properties > jboss-logging.properties > log4j.properties > log4j.xml > jboss-log4j.xml > All of these are stale because they are based on Log4j 1.x format which died about 8 years ago (along with using properties files for logging configuration). > Modern popular options include Logback (with SLF4J), JBoss Logging and Log4j 2.x. > *I regularly see WildFly users (included RH employees) that struggle to configure the logging configuration of their WildFly apps.* Spring Boot does not have this problem. _To fix this, WildFly should support logback.xml for Per deployment logging too._ > When I add a logback.xml in my war's WEB-INF/classes directory and explicitly add the logback-classic.jar in WEB-INF/lib directory - which works to configure Logback in any other JVM - then WildFly ignores it (~ it says GFY). My logs doesn't show up and developing on WildfFly is a pain due to blindness. > Fake solution: Configuring the log files per WildFly installation is not practical for developers (it is for sys admins): the log configuration should be in my war's sources on github, so other developers automatically have it without needing to jump to wildfly installation hoops (which is sometimes not possible, think OpenShift). > Although it's ok that WildFly favors JBoss Logging, it should not dictate it and support other logging systems such as Logback too for the war files at least (= per deployment). > [1] https://docs.jboss.org/author/display/WFLY10/Logging+Configuration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 June 2017