July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1602) Elytron integration with JMX

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1602?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1602: ------------------------------------- Fix Version/s: 3.0.0.Alpha5 (was: 3.0.0.Alpha4) > Elytron integration with JMX > ---------------------------- > > Key: WFCORE-1602 > URL: https://issues.jboss.org/browse/WFCORE-1602 > Project: WildFly Core > Issue Type: Feature Request > Components: JMX > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1600) Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1600?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1600: ------------------------------------- Fix Version/s: 3.0.0.Alpha5 (was: 3.0.0.Alpha4) > Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances. > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1600 > URL: https://issues.jboss.org/browse/WFCORE-1600 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha5 > > > These are for use when security realms are directly referenced, although Elytron types these should not be advertised as capabilities as these are for specific backwards compatibility requirements and not to increase their use as Elytron capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1670) Upgrade to JBoss DMR 1.4.0.Beta1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1670?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1670: ------------------------------------- Fix Version/s: 3.0.0.Alpha5 (was: 3.0.0.Alpha4) > Upgrade to JBoss DMR 1.4.0.Beta1 > -------------------------------- > > Key: WFCORE-1670 > URL: https://issues.jboss.org/browse/WFCORE-1670 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha5 > > > Pick up DMR-9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6892) Access logging for EJBs

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-6892: ---------------------------------------- FYI how audit logging fits in with Elytron is still something we need to work though but +1 on something common, and +1 on appropriate separation. > Access logging for EJBs > ----------------------- > > Key: WFLY-6892 > URL: https://issues.jboss.org/browse/WFLY-6892 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Labels: affects_elytron > > Access logging for EJB requests similar to Web access logging would be very useful. > Possibly something like: > {code} > [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6892) Access logging for EJBs

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6892: ----------------------------------- Labels: affects_elytron (was: ) > Access logging for EJBs > ----------------------- > > Key: WFLY-6892 > URL: https://issues.jboss.org/browse/WFLY-6892 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Labels: affects_elytron > > Access logging for EJB requests similar to Web access logging would be very useful. > Possibly something like: > {code} > [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1592) PropertiesFileLoader persists entries after deletion

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1592?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-1592: ----------------------------------- add-user is working fine, as it only enables / disables users by commenting them out then resaving the file, so I think we're good there. I'll have a quick look in the console too for any user management. > PropertiesFileLoader persists entries after deletion > ---------------------------------------------------- > > Key: WFCORE-1592 > URL: https://issues.jboss.org/browse/WFCORE-1592 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.Final, 2.2.0.CR1, 2.2.0.CR2, 3.0.0.Alpha1 > Reporter: Max Barkley > Assignee: Ken Wills > Fix For: 3.0.0.Alpha4, 2.2.0.Final > > > There is a bug in PropertiesFileLoader#persistProperties, specifically [here|https://github.com/wildfly/wildfly-core/blob/master/domain-managemen...]. Because of the write call in the else block, properties are persisted to the file even after they have been deleted in memory. > [Here|https://github.com/psiroky/uberfire/blob/2811baeac64805646d3943a096e...] is a fixed implementation of persistProperties that we are using as a workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6892) Access logging for EJBs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6892: ---------------------------------------- The management audit log needs to be clearly distinguished from other forms of logging in order to support the RBAC requirement that operations against its management resources can be limited to users in the Auditor role. This doesn't mean the way it is configured is set in stone. It does mean though that the definition of the resources must be distinct from those of other logging resources, at least to the extent that the definition includes necessary information to identify the resource as being related to management audit logging. Currently what resource patterns are related to management audit logging is hard coded in the RBAC impl. > Access logging for EJBs > ----------------------- > > Key: WFLY-6892 > URL: https://issues.jboss.org/browse/WFLY-6892 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > > Access logging for EJB requests similar to Web access logging would be very useful. > Possibly something like: > {code} > [date-time] [host/IP of caller] [EJB Name] [EJB Method] [invocation id] Request Received ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Starting Invocation ... > [date-time] [host/IP of caller] [EJB Name] [EJB Method] invocation id] Finished Invocation ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-54) Support for stronger hashes as alternatives to MD5

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-54?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-54: -------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Support for stronger hashes as alternatives to MD5 > -------------------------------------------------- > > Key: ELY-54 > URL: https://issues.jboss.org/browse/ELY-54 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > Presently Digest authentication is based on MD5 - however we should either update the mechanism or add new mechanisms to support the use of stronger hashes. > As this library is used both client and server side installations that require the stronger hashes can just ensure the client and server have the latest version of this library - installations that still require interaction with MD5 will need to ensure that it is still available as a mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-53) GSSAPI Make Delegated Credential Available

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-53?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-53: -------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > GSSAPI Make Delegated Credential Available > ------------------------------------------ > > Key: ELY-53 > URL: https://issues.jboss.org/browse/ELY-53 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > The server side of the mechanism can receive a delegated credential but there is no way to obtain it, we should provide a way for it to be obtained or provided. > _Note: This may be an Elytron integration point rather than something supported in the pure SASL mechanism._ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-211) Client-side trust store configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-211?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-211: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Client-side trust store configuration > ------------------------------------- > > Key: ELY-211 > URL: https://issues.jboss.org/browse/ELY-211 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta8 > > > Lest I forget. The client needs the ability to supplement the default trust store, to restrict the set of acceptable peer certificates/signers, for mutual authentication purposes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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