December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7081) Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true"

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7081?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-7081: -------------------------------------- [~dlofthouse] are you going to remove the SSLEngine wrapping in Elytron, or do I need to hack around this in Undertow? > Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true" > ------------------------------------------------------------------------------------------ > > Key: WFLY-7081 > URL: https://issues.jboss.org/browse/WFLY-7081 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > When I want to use HTTPS settings in combination with Elytron subsystem then I have to set "enable-http2" to "false" value. > For settings I followed this blog post http://darranl.blogspot.cz/2016/02/wildfly-elytron-ssl-configuration.html > And as keystore I used default application.keystore -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2106) Allow expressions in relative-to of keystore

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2106?page=com.atlassian.jira.plugi... ] Philippe Marschall closed WFCORE-2106. -------------------------------------- Resolution: Won't Fix Relative to is a service dependency which means we do not support expressions for this attribute. > Allow expressions in relative-to of keystore > -------------------------------------------- > > Key: WFCORE-2106 > URL: https://issues.jboss.org/browse/WFCORE-2106 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Philippe Marschall > > All attributes on the keystore element including the path element > support expressions with the exception of the relative-to element. > This seem inconsistent and forces us to have a more complicated than > necessary expression in the path element instead of being able to split > it between the path and relative-to element. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2106) Allow expressions in relative-to of keystore

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2106?page=com.atlassian.jira.plugi... ] Philippe Marschall updated WFCORE-2106: --------------------------------------- Component/s: Domain Management > Allow expressions in relative-to of keystore > -------------------------------------------- > > Key: WFCORE-2106 > URL: https://issues.jboss.org/browse/WFCORE-2106 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Philippe Marschall > > All attributes on the keystore element including the path element > support expressions with the exception of the relative-to element. > This seem inconsistent and forces us to have a more complicated than > necessary expression in the path element instead of being able to split > it between the path and relative-to element. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2106) Allow expressions in relative-to of keystore

by Philippe Marschall (JIRA)

Philippe Marschall created WFCORE-2106: ------------------------------------------ Summary: Allow expressions in relative-to of keystore Key: WFCORE-2106 URL: https://issues.jboss.org/browse/WFCORE-2106 Project: WildFly Core Issue Type: Enhancement Reporter: Philippe Marschall All attributes on the keystore element including the path element support expressions with the exception of the relative-to element. This seem inconsistent and forces us to have a more complicated than necessary expression in the path element instead of being able to split it between the path and relative-to element. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2105) Raise log level of deprecations to WARN

by Philippe Marschall (JIRA)

Philippe Marschall created WFCORE-2105: ------------------------------------------ Summary: Raise log level of deprecations to WARN Key: WFCORE-2105 URL: https://issues.jboss.org/browse/WFCORE-2105 Project: WildFly Core Issue Type: Enhancement Reporter: Philippe Marschall We believe the log level of log level of deprecations should be WARN instead of INFO. We were using a deprecated attribute and almost didn't see the message in the see of INFO messages. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4296) remove _ds.xml deployment support

by Gonzalo Alonso (JIRA)

[ https://issues.jboss.org/browse/WFLY-4296?page=com.atlassian.jira.plugin.... ] Gonzalo Alonso edited comment on WFLY-4296 at 12/10/16 1:09 PM: ---------------------------------------------------------------- once read arguments for and against this to be deprecated, +I also disagree+ with suppress this feature because it implies removing some advantages over other application servers. Because of safety and maintanibility, I think its more sensible to mantain each datasource for an application just writting a specificfile for that application (-ds.xml), much better than making changes in a big file where we must remember each change and how that affects to each application. was (Author: albus): once read arguments for and against this to be deprecated,* I also disagree *with suppress this feature because it implies removing some advantages over other application servers. Because of safety and maintanibility, I think its more sensible to mantain each datasource for an application just writting a specificfile for that application (-ds.xml), much better that making changes in a big file where we must remember each change and how that affects to each application. > remove _ds.xml deployment support > --------------------------------- > > Key: WFLY-4296 > URL: https://issues.jboss.org/browse/WFLY-4296 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Stefano Maestri > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4296) remove _ds.xml deployment support

by Gonzalo Alonso (JIRA)

[ https://issues.jboss.org/browse/WFLY-4296?page=com.atlassian.jira.plugin.... ] Gonzalo Alonso commented on WFLY-4296: -------------------------------------- once read arguments for and against this to be deprecated,* I also disagree *with suppress this feature because it implies removing some advantages over other application servers. Because of safety and maintanibility, I think its more sensible to mantain each datasource for an application just writting a specificfile for that application (-ds.xml), much better that making changes in a big file where we must remember each change and how that affects to each application. > remove _ds.xml deployment support > --------------------------------- > > Key: WFLY-4296 > URL: https://issues.jboss.org/browse/WFLY-4296 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Stefano Maestri > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7778) Remoting identity propagation does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7778: ----------------------------- Summary: Remoting identity propagation does not work with Elytron (was: Remoting does not work with Elytron) > Remoting identity propagation does not work with Elytron > -------------------------------------------------------- > > Key: WFLY-7778 > URL: https://issues.jboss.org/browse/WFLY-7778 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Critical > > Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. > Identity is unauthorized on server side. > Remoting does not work because it is not implemented - this issue created primary for tests ignore issue reference. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7778) Remoting does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7778: ----------------------------- Steps to Reproduce: Tests: (after modification to use Elytron instead of legacy subystem) org.jboss.as.test.integration.ejb.security.testAuthentication() org.jboss.as.test.integration.ejb.security.testAuthentication_BadPwd() org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans() org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans_ReAuth_BadPwd() (and a lot of other, most of tests using EJB) was: Tests: (after modification to use Elytron instead of legacy subystem) org.jboss.as.test.integration.ejb.security.testAuthentication() org.jboss.as.test.integration.ejb.security.testAuthentication_BadPwd() org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans() org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans_ReAuth_BadPwd() > Remoting does not work with Elytron > ----------------------------------- > > Key: WFLY-7778 > URL: https://issues.jboss.org/browse/WFLY-7778 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Critical > > Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. > Identity is unauthorized on server side. > Remoting does not work because it is not implemented - this issue created primary for tests ignore issue reference. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7779) ReAuth does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7779?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7779: ----------------------------- Description: Following way of change identity from servlet does not work: {code:java} LoginContext lc = getCLMLoginContext(username, password); lc.login(); {code} > ReAuth does not work with Elytron > --------------------------------- > > Key: WFLY-7779 > URL: https://issues.jboss.org/browse/WFLY-7779 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > > Following way of change identity from servlet does not work: > {code:java} > LoginContext lc = getCLMLoginContext(username, password); > lc.login(); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 December 2016