January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3382) Further Enhance Elytron Permission Configuration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3382?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3382: ------------------------------------- Fix Version/s: 4.0.0.Alpha7 (was: 4.0.0.Alpha6) > Further Enhance Elytron Permission Configuration > ------------------------------------------------ > > Key: WFCORE-3382 > URL: https://issues.jboss.org/browse/WFCORE-3382 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Fix For: 4.0.0.Alpha7 > > > This has currently been simplified to a single resource for the out of the box configuration, however this brings issues as now permissions are duplicated so modifications need to be replicated instead of to a single location. > Finding a way for the default required permissions to be defined in one location could help eliminate the duplication. > We could also consider going one step further and subsystems register the default permissions that should be granted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3360) Eliminate org.wildfly.extension.elytron.ProviderUtil

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3360?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3360: ------------------------------------- Fix Version/s: 4.0.0.Alpha7 (was: 4.0.0.Alpha6) > Eliminate org.wildfly.extension.elytron.ProviderUtil > ---------------------------------------------------- > > Key: WFCORE-3360 > URL: https://issues.jboss.org/browse/WFCORE-3360 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha7 > > > WildFly Elytron contains a public utility class org.wildfly.security.util.ProviderUtil for the same purpose, we should use the code within WildFly Elytron and not custom code within the subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3527) Remove OSGi obsolete code

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3527?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3527: ------------------------------------- Fix Version/s: 4.0.0.Alpha7 (was: 4.0.0.Alpha6) > Remove OSGi obsolete code > ------------------------- > > Key: WFCORE-3527 > URL: https://issues.jboss.org/browse/WFCORE-3527 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 4.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 4.0.0.Alpha7 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3519) Add JASPI Module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3519?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3519: ------------------------------------- Fix Version/s: 4.0.0.Alpha7 (was: 4.0.0.Alpha6) > Add JASPI Module > ---------------- > > Key: WFCORE-3519 > URL: https://issues.jboss.org/browse/WFCORE-3519 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 4.0.0.Alpha7 > > > (Copy from WildFly) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-82) PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-82?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-82: -------------------------------- Fix Version/s: (was: 2.1.0.Alpha6) > PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy > -------------------------------------------------------------------- > > Key: LOGMGR-82 > URL: https://issues.jboss.org/browse/LOGMGR-82 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > > The rotation tests seem to fail at random days and times. The test {{testPeriodicAndSizeRotate}} needs to be looked at before re-enabling it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-190) The SocketFactory should be allowed to be set on the SocketHandler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-190?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-190: --------------------------------- Fix Version/s: 2.1.0.Alpha6 > The SocketFactory should be allowed to be set on the SocketHandler > ------------------------------------------------------------------ > > Key: LOGMGR-190 > URL: https://issues.jboss.org/browse/LOGMGR-190 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.0.Alpha6 > > > The {{SocketHandler}} should allow for the {{SocketFactory}} to be set. This will be useful in WildFly where a {{SocketFactory}} may be a capability of another subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-190) The SocketFactory should be allowed to be set on the SocketHandler

by James Perkins (JIRA)

James Perkins created LOGMGR-190: ------------------------------------ Summary: The SocketFactory should be allowed to be set on the SocketHandler Key: LOGMGR-190 URL: https://issues.jboss.org/browse/LOGMGR-190 Project: JBoss Log Manager Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins The {{SocketHandler}} should allow for the {{SocketFactory}} to be set. This will be useful in WildFly where a {{SocketFactory}} may be a capability of another subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-151) SyslogHandler should allow to set custom SSLSocketFactory

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-151?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-151: ------------------------------------ Assignee: James Perkins > SyslogHandler should allow to set custom SSLSocketFactory > --------------------------------------------------------- > > Key: LOGMGR-151 > URL: https://issues.jboss.org/browse/LOGMGR-151 > Project: JBoss Log Manager > Issue Type: Enhancement > Affects Versions: 2.0.5.Final > Reporter: Jan Kalina > Assignee: James Perkins > > As part of Wildfly Elytron integration would be useful to allow to put custom *SSLSocketFactory* into *SyslogHandler*. > It would allow to use *ssl-context* defined in elytron (with custom configuration of CAs, truststore, keystore) for syslog over TLS. > (SyslogHandler is used for syslog audit logging in Elytron too - and currently no way to put elytron ssl-context into) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-189) Allow the instances to be exposed from the configuration API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-189?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-189: --------------------------------- Description: The configuration API should return the instance created via the API. This will allow LOGMGR-188 to be reverted and simplify how the persisted configuration will be written. Changes to the object instance will not be reflected in the configuration API. This is however the desired behavior for properties that should not be written to the configuration file. An example use case of this will be for WildFly. A {{SocketHandler}} may be created based on an {{SSLContext}} configured in Elytron. This handler can be created without the configuration API and the handler will be set on a {{DelayedHandler}} instance that will be created via the configuration API. was:The configuration API should return the instance created via the API. This will allow LOGMGR-188 to be reverted and simplify how the persisted configuration will be written. > Allow the instances to be exposed from the configuration API > ------------------------------------------------------------ > > Key: LOGMGR-189 > URL: https://issues.jboss.org/browse/LOGMGR-189 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Assignee: James Perkins > > The configuration API should return the instance created via the API. This will allow LOGMGR-188 to be reverted and simplify how the persisted configuration will be written. Changes to the object instance will not be reflected in the configuration API. This is however the desired behavior for properties that should not be written to the configuration file. > An example use case of this will be for WildFly. A {{SocketHandler}} may be created based on an {{SSLContext}} configured in Elytron. This handler can be created without the configuration API and the handler will be set on a {{DelayedHandler}} instance that will be created via the configuration API. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-189) Allow the instances to be exposed from the configuration API

by James Perkins (JIRA)

James Perkins created LOGMGR-189: ------------------------------------ Summary: Allow the instances to be exposed from the configuration API Key: LOGMGR-189 URL: https://issues.jboss.org/browse/LOGMGR-189 Project: JBoss Log Manager Issue Type: Feature Request Reporter: James Perkins Assignee: James Perkins The configuration API should return the instance created via the API. This will allow LOGMGR-188 to be reverted and simplify how the persisted configuration will be written. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018