August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.Final) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.2.0.Beta1 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-681) Hide private packages from generated javadoc.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-681?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-681: --------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.Final) > Hide private packages from generated javadoc. > --------------------------------------------- > > Key: ELY-681 > URL: https://issues.jboss.org/browse/ELY-681 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta1 > > > We may want two profiles so we can generate a full javadoc and a 'public' javadoc. > The 'public' javadoc should be the default one generated and should exclude the following packages: - > org.wildfly.security._private > org.wildfly.security.asn1 > org.wildfly.security.auth.realm > org.wildfly.security.auth.realm.* > org.wildfly.security.authz.jacc > org.wildfly.security.credential.store.impl > org.wildfly.security.security.digest > org.wildfly.security.http.impl > org.wildfly.security.security.keystore > org.wildfly.security.mechanism.oauth2 > org.wildfly.security.mechanism.scram > org.wildfly.security.password.impl > org.wildfly.security.password.util > org.wildfly.security.pem > org.wildfly.security.sasl > org.wildfly.security.sasl.* (Except util) > org.wildfly.security.util > org.wildfly.security.util_private > org.wildfly.security.x500 > org.wildfly.security.x500.cert -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-659) Make all mechanism implementations final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-659?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-659: --------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.Final) > Make all mechanism implementations final > ---------------------------------------- > > Key: ELY-659 > URL: https://issues.jboss.org/browse/ELY-659 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Mechanisms, HTTP, SASL > Reporter: David Lloyd > Priority: Critical > Fix For: 1.2.0.Beta1 > > > It is very important to make all the mechanism implementations final. Relatedly, they should have no protected members. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-533?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-533: --------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.Final) > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.jboss.org/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta1 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1000) Release WildFly Elytron 1.1.0.Final

by Darran Lofthouse (JIRA)

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

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2147?page=com.atlassian.jira.plugi... ] jaikiran pai commented on WFCORE-2147: -------------------------------------- Although this appears to be easy to do, it isn't. That has to do with the way and where this property replacement related logic resides and how it's tightly integrated currently with EE subsystem which is outside of wildfly core and security manager subsystem. [~brian.stansberry] has explained this very thing in one other similar JIRA here WFCORE-1295 > Impossible to use environment variables or system properties in permissions.xml > ------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.jboss.org/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Adrian Boangiu > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2147?page=com.atlassian.jira.plugi... ] jaikiran pai updated WFCORE-2147: --------------------------------- Component/s: (was: Security) > Impossible to use environment variables or system properties in permissions.xml > ------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.jboss.org/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Adrian Boangiu > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2147?page=com.atlassian.jira.plugi... ] jaikiran pai updated WFCORE-2147: --------------------------------- Component/s: Security > Impossible to use environment variables or system properties in permissions.xml > ------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.jboss.org/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Adrian Boangiu > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-25) Unable to specify feature pack's contents and modules to include

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-25?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFBUILD-25: ----------------------------------- Description: The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": {code} <server-provisioning> <feature-packs> <feature-pack> <modules include="false"> <filter pattern="*/me/include/main/module.xml" include="true"/> </contents> <contents include="false"> <filter pattern="include.me" include="true"/> </contents> </feature-pack> </feature-packs> </server-provisioning> {code} The issue is that whenever "include" attribute in <modules/> or <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but char "?" is replaced by "." in the expression, so no chance to use "?!" or "?=". was: The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": {code} <server-provisioning> <feature-packs> <feature-pack> <contents include="false"> <filter pattern="include.me" include="true"/> </contents> </feature-pack> </feature-packs> </server-provisioning> {code} The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". > Unable to specify feature pack's contents and modules to include > ---------------------------------------------------------------- > > Key: WFBUILD-25 > URL: https://issues.jboss.org/browse/WFBUILD-25 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": > {code} > <server-provisioning> > <feature-packs> > <feature-pack> > <modules include="false"> > <filter pattern="*/me/include/main/module.xml" include="true"/> > </contents> > <contents include="false"> > <filter pattern="include.me" include="true"/> > </contents> > </feature-pack> > </feature-packs> > </server-provisioning> > {code} > The issue is that whenever "include" attribute in <modules/> or <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... > A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but char "?" is replaced by "." in the expression, so no chance to use "?!" or "?=". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-25) Unable to specify feature pack's contents and modules to include

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-25?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFBUILD-25: ----------------------------------- Summary: Unable to specify feature pack's contents and modules to include (was: Unable to specify a feature pack content to include) > Unable to specify feature pack's contents and modules to include > ---------------------------------------------------------------- > > Key: WFBUILD-25 > URL: https://issues.jboss.org/browse/WFBUILD-25 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > The following server-provisioning.xml example should filter the feature pack's content, unless file path matches pattern "include.me": > {code} > <server-provisioning> > <feature-packs> > <feature-pack> > <contents include="false"> > <filter pattern="include.me" include="true"/> > </contents> > </feature-pack> > </feature-packs> > </server-provisioning> > {code} > The issue is that whenever "include" attribute in <contents /> element is set to "false" no filters are able to include content, see https://github.com/wildfly/wildfly-build-tools/blob/master/provisioning/s... > A possible workaround for this would be to use filters with negative regex patterns, and include set as false, but "?!" is not considered and the "?" is replaced by ".". -- 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 August 2017