[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
[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
[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
[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