September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9294) Add encryption/authentication configuration for infinispan remote cache store

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9294?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9294: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > Add encryption/authentication configuration for infinispan remote cache store > ----------------------------------------------------------------------------- > > Key: WFLY-9294 > URL: https://issues.jboss.org/browse/WFLY-9294 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1246) The elytron-1_0.xsd has elements the parser does not accept

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1246?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1246: ------------------------------- Assignee: (was: Jan Kalina) > The elytron-1_0.xsd has elements the parser does not accept > ----------------------------------------------------------- > > Key: ELY-1246 > URL: https://issues.jboss.org/browse/ELY-1246 > Project: WildFly Elytron > Issue Type: Bug > Reporter: James Perkins > > There are elements in the {{elytron-1_0.xsd}} that the parser does not accept. While I didn't check them all here are at least a few that are in the XSD that the parser will reject: > * {{allow-sasl-mechanisms}} > * {{allow-all-sasl-mechanisms}} > * {{forbid-sasl-mechanisms}} > This may be all of them, but it should likely be validated that those are the only ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container/remote-cache configuration to Infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6634: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Add remote-cache-container/remote-cache configuration to Infinispan subsystem > ----------------------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1082) Documentation is missing in elytron-1_0.xsd

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1082?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1082: --------------------------------- Just note the same documentation will need to be added into *elytron-client-1_1.xsd* which will be added as part of ELY-1354 in https://github.com/wildfly-security/wildfly-elytron/pull/978 soon. > Documentation is missing in elytron-1_0.xsd > ------------------------------------------- > > Key: ELY-1082 > URL: https://issues.jboss.org/browse/ELY-1082 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta34 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Critical > > XSD file {{elytron-1_0.xsd}} [1] includes almost no documentation. If this XSD is included in server distribution (as {{docs/schema/elytron-1_0.xsd}}) then it affects user experience. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1246) The elytron-1_0.xsd has elements the parser does not accept

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1246?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1246: --------------------------------- Mentioned elements are already removed, just should be checked whether there is no more XSD elements, which are not accepted by ElytronXmlParser. [~ivassile] as you are already going through individual XSD items while documenting them in ELY-1082, dont you want to take this one too? > The elytron-1_0.xsd has elements the parser does not accept > ----------------------------------------------------------- > > Key: ELY-1246 > URL: https://issues.jboss.org/browse/ELY-1246 > Project: WildFly Elytron > Issue Type: Bug > Reporter: James Perkins > Assignee: Jan Kalina > > There are elements in the {{elytron-1_0.xsd}} that the parser does not accept. While I didn't check them all here are at least a few that are in the XSD that the parser will reject: > * {{allow-sasl-mechanisms}} > * {{allow-all-sasl-mechanisms}} > * {{forbid-sasl-mechanisms}} > This may be all of them, but it should likely be validated that those are the only ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3296) Ephemeral port number (port="0") should not be affected by port offset

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3296?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFCORE-3296: ----------------------------------- Description: Port 0 is almost universally considered a wildcard port/indeterminate port/ephemeral/port chosen by the OS and obviously applying an offset to such port (e.g. offset of -100) will fail on multiple fronts, e.g.: {noformat} Caused by: java.lang.IllegalArgumentException: port out of range:-100 {noformat} This is a regression introduced in https://issues.jboss.org/browse/WFLY-2345 based on discussion on https://developer.jboss.org/message/842406#842407 in PR https://github.com/wildfly/wildfly/pull/5307/files#diff-1a9ef995f085779b0... The original condition was also not really correct, since we allow negative and positive port offsets, the correct condition really is {code}if (!isFixedPort && port != 0) {{code} was: Port 0 is almost universally considered an indeterminate port/ephemeral/port chosen by the OS and obviously applying an offset to such port (e.g. offset of -100) will fail on multiple fronts, e.g.: {noformat} Caused by: java.lang.IllegalArgumentException: port out of range:-100 {noformat} This is a regression introduced in https://issues.jboss.org/browse/WFLY-2345 based on discussion on https://developer.jboss.org/message/842406#842407 in PR https://github.com/wildfly/wildfly/pull/5307/files#diff-1a9ef995f085779b0... The original condition was also not really correct, since we allow negative and positive port offsets, the correct condition really is {{if (!isFixedPort && port != 0) {...}} > Ephemeral port number (port="0") should not be affected by port offset > ---------------------------------------------------------------------- > > Key: WFCORE-3296 > URL: https://issues.jboss.org/browse/WFCORE-3296 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.2.Final > Reporter: Radoslav Husar > > Port 0 is almost universally considered a wildcard port/indeterminate port/ephemeral/port chosen by the OS and obviously applying an offset to such port (e.g. offset of -100) will fail on multiple fronts, e.g.: > {noformat} > Caused by: java.lang.IllegalArgumentException: port out of range:-100 > {noformat} > This is a regression introduced in https://issues.jboss.org/browse/WFLY-2345 based on discussion on https://developer.jboss.org/message/842406#842407 in PR https://github.com/wildfly/wildfly/pull/5307/files#diff-1a9ef995f085779b0... > The original condition was also not really correct, since we allow negative and positive port offsets, the correct condition really is {code}if (!isFixedPort && port != 0) {{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3296) Ephemeral port number (port="0") should not be affected by port offset

by Radoslav Husar (JIRA)

Radoslav Husar created WFCORE-3296: -------------------------------------- Summary: Ephemeral port number (port="0") should not be affected by port offset Key: WFCORE-3296 URL: https://issues.jboss.org/browse/WFCORE-3296 Project: WildFly Core Issue Type: Bug Affects Versions: 3.0.2.Final Reporter: Radoslav Husar Port 0 is almost universally considered an indeterminate port/ephemeral/port chosen by the OS and obviously applying an offset to such port (e.g. offset of -100) will fail on multiple fronts, e.g.: {noformat} Caused by: java.lang.IllegalArgumentException: port out of range:-100 {noformat} This is a regression introduced in https://issues.jboss.org/browse/WFLY-2345 based on discussion on https://developer.jboss.org/message/842406#842407 in PR https://github.com/wildfly/wildfly/pull/5307/files#diff-1a9ef995f085779b0... The original condition was also not really correct, since we allow negative and positive port offsets, the correct condition really is {{if (!isFixedPort && port != 0) {...}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1024) Match rules do not allow matching any-or-no user

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1024?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1024: --------------------------------- Is not this an equivalent of no user matching rule specified? > Match rules do not allow matching any-or-no user > ------------------------------------------------ > > Key: ELY-1024 > URL: https://issues.jboss.org/browse/ELY-1024 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1368) Elytron CommandCredentialSource closes STD_ERR stream without consuming it

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1368?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1368: ---------------------------------- Fix Version/s: 1.2.0.Beta4 > Elytron CommandCredentialSource closes STD_ERR stream without consuming it > -------------------------------------------------------------------------- > > Key: ELY-1368 > URL: https://issues.jboss.org/browse/ELY-1368 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 1.2.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta4 > > > External commands used for retrieving Elytron credentials may fail due to closed error stream. > The {{CommandCredentialSource}} closes STD_ERR stream without consuming it. > Elytron unit test {{CommandCredentialSourceTest}} (which executes an external java program) hits this issue in some environments. Log contains; > {noformat} > 11:30:29,201 TRACE (main) [org.wildfly.security] <CommandCredentialSource.java:114> Exit code from password command = 141 > {noformat} > The issue was investigated in this PR. You can find more details there: > https://github.com/wildfly-security/wildfly-elytron/pull/981 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1368) Elytron CommandCredentialSource closes STD_ERR stream without consuming it

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1368?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse moved JBEAP-13173 to ELY-1368: ----------------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1368 (was: JBEAP-13173) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Credential Store (was: Security) Affects Version/s: 1.2.0.Beta3 (was: 7.1.0.CR1) > Elytron CommandCredentialSource closes STD_ERR stream without consuming it > -------------------------------------------------------------------------- > > Key: ELY-1368 > URL: https://issues.jboss.org/browse/ELY-1368 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 1.2.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > > External commands used for retrieving Elytron credentials may fail due to closed error stream. > The {{CommandCredentialSource}} closes STD_ERR stream without consuming it. > Elytron unit test {{CommandCredentialSourceTest}} (which executes an external java program) hits this issue in some environments. Log contains; > {noformat} > 11:30:29,201 TRACE (main) [org.wildfly.security] <CommandCredentialSource.java:114> Exit code from password command = 141 > {noformat} > The issue was investigated in this PR. You can find more details there: > https://github.com/wildfly-security/wildfly-elytron/pull/981 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 September 2017