February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1159) Allow configure SSL connection in stanalone.xml for email servers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1159?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1159: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Allow configure SSL connection in stanalone.xml for email servers > ----------------------------------------------------------------- > > Key: WFLY-1159 > URL: https://issues.jboss.org/browse/WFLY-1159 > Project: WildFly > Issue Type: Sub-task > Components: Mail > Reporter: Alexey Volkov > Assignee: Peter Skopek > Fix For: 12.0.0.Final > > > Allow to configure SSL connection to email servers into stanalone.xml > Here is the discussion into community https://community.jboss.org/thread/205364 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-466) Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-466?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-466: ------------------------------ Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Detect JBossWS Configuration for @PermitAll endpoints within Undertow subsystem. > -------------------------------------------------------------------------------- > > Key: WFLY-466 > URL: https://issues.jboss.org/browse/WFLY-466 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Final > > > UNDERTOW-38 has added the possibility of deploying web applications where authentication is mandated but no authorization checks are performed - this is required for integration use cases such as EJB endpoints where authorization checks are being left to the EJB container. > This task is to update the Undertow susbsystem to detect this scenario and enable the new mode for UNDERTOW-38. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-383) Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-383?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-383: ------------------------------ Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase > ----------------------------------------------------------------- > > Key: WFLY-383 > URL: https://issues.jboss.org/browse/WFLY-383 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Final > > > I have marked this test as "@Ignore"d as I do not believe the capability that is being tested is actually valid. > I can not find any evidence that we ever intended for a role to role mapping within the jboss-web.xml instead we only intended a principal to role mapping. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4056) Graceful shutdown for JMS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4056?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4056: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Graceful shutdown for JMS > ------------------------- > > Key: WFLY-4056 > URL: https://issues.jboss.org/browse/WFLY-4056 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Stuart Douglas > Assignee: Jeff Mesnil > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3064) Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3064?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3064: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-3064 > URL: https://issues.jboss.org/browse/WFLY-3064 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Final > > > A new test case was added under WFLY-3063 that demonstrates the correct way to do this so now remove the original way that depended on internal APIs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3463) org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3463?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3463: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties > ---------------------------------------------------------------------------------- > > Key: WFLY-3463 > URL: https://issues.jboss.org/browse/WFLY-3463 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 9.0.0.CR1 > Reporter: Scott Marlow > Assignee: Alessio Soldano > Fix For: 12.0.0.Final > > > During TCK testing (with security-manager enabled), I am seeing a java.security.AccessControlException: WFSM000001: Permission check failed for ("java.io.FilePermission" "/qa/tools/opt/x86_64/jdk1.7.0_60/jre/lib/wsdl.properties" "read") > from org.apache.cxf.wsdl11.WSDLManagerImpl. > Some related comments from irc: > {quote} > http://sourceforge.net/p/wsdl4j/patches/1/ > <asoldano> smarlow, I'm currently working around the problem (when running with security manager on) by setting "-Djavax.wsdl.factory.WSDLFactory=com.ibm.wsdl.factory.WSDLFactoryImpl" when starting the jvm > {quote} > Seems related to [https://issues.apache.org/jira/browse/TUSCANY-3925] which also has a patch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2102) Improve deployment annotation parsing error message

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2102?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2102: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Improve deployment annotation parsing error message > ----------------------------------------------------- > > Key: WFLY-2102 > URL: https://issues.jboss.org/browse/WFLY-2102 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Brad Maxwell > Fix For: 12.0.0.Final > > Attachments: test-WFLY-2102.jar > > > Improve deployment annotation parsing error message > Code such as this below, will error with IllegalArgumentException: Empty name segment is not allowed for env. The env is not enough information to identify what the issue is. > @Singleton > @Startup > public class TestEJB { > @Resource(name="/queue/test") > private Queue queue; > } > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for env > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:141) > at org.jboss.as.ee.component.OptionalLookupInjectionSource.getResourceValue(OptionalLookupInjectionSource.java:84) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:1019) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:998) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:138) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1598: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Out of the box SSL - or shortly after. > -------------------------------------- > > Key: WFLY-1598 > URL: https://issues.jboss.org/browse/WFLY-1598 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Priority: Critical > Labels: management_security,, management_sso > Fix For: 12.0.0.Final > > > There are various reasons that we do not support SSL/TLS out of the box e.g. > - If we ship a default keystore then everyone has access to the private key. > - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead. > This issue is to explorer other options to encourage their use and make it easier to configure. > As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5550: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Formalize web session clustering modules into a proper subsystem > ---------------------------------------------------------------- > > Key: WFLY-5550 > URL: https://issues.jboss.org/browse/WFLY-5550 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.CR3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose. > Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation. > The subsystem would define the requisite cache-container, exposed as a capability. > This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name). jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5497) Add <distributable/> to shared-session-config schema

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5497?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5497: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Add <distributable/> to shared-session-config schema > ---------------------------------------------------- > > Key: WFLY-5497 > URL: https://issues.jboss.org/browse/WFLY-5497 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Currently, the shared-session-config does not indicate whether a distributable or non-distributable session manager should be used. Consequently, we assign the session manager implementation based on the availability of the module providing the distributed implementation. Since the default infinispan web session configuration attempts to passivate sessions on shutdown, users will see NotSerializableExceptions on shutdown if they use non-serializable session attributes - even if their web applications do not define themselves as being <distributable/>. > To clarify this ambiguity, we should add a <distributable/> element (a la web.xml) to the shared-session-config schema to determine which session manager implementation to use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018