July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-583) Add ability for outbound clients to directly consume IdentityCredentials

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-583?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-583: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Add ability for outbound clients to directly consume IdentityCredentials > ------------------------------------------------------------------------ > > Key: ELY-583 > URL: https://issues.jboss.org/browse/ELY-583 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta8 > > > Outbound clients can gain substantial flexibility by being able to use {{IdentityCredentials}} directly. This allows a non-type-specific object like a {{byte[]}} to be interpreted as many different types of credentials. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-582) Logic error in functional cast methods in Credential, Evidence, Password

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-582?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-582: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Logic error in functional cast methods in Credential, Evidence, Password > ------------------------------------------------------------------------ > > Key: ELY-582 > URL: https://issues.jboss.org/browse/ELY-582 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta8 > > > There's a bug in algorithm handling in the Credential, Evidence, and Password type hierarchies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-604) SecurityProviderSaslClientFactory and ServiceLoaderSaslClientFactory lose mech order

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-604?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-604: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > SecurityProviderSaslClientFactory and ServiceLoaderSaslClientFactory lose mech order > ------------------------------------------------------------------------------------ > > Key: ELY-604 > URL: https://issues.jboss.org/browse/ELY-604 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta8 > > > Preserve order the way the JDK does: query the factories one by one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-606) Wrap the match elements with an outer match element.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-606?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-606: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Wrap the match elements with an outer match element. > ---------------------------------------------------- > > Key: ELY-606 > URL: https://issues.jboss.org/browse/ELY-606 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta8 > > > For each match type we support at most one definition of each - by adding a wrapper element we can use xsd:all to more accurately reflect this. -- 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: ----------------------------------- Yep, I'll test this against full and make sure its still working. > 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on WFLY-6892 at 7/28/16 5:12 PM: -------------------------------------------------------------- Just adding my same comment here as this would likely be looked at first when the work starts. {quote} One thing we should start to consider is where/how these will be configured. Currently management access logs are configured under {{/core-service=management/access=audit}} and web access logging is configured under {{/subsystem=undertow/server=default-server/host=default-host/setting=access-log}}. The resources also have different models, log to different locations, etc. We should consider whether there should be a central place these can be configured or not. {quote} To follow up on that too there is currently a log viewer that can view the plain text versions of only the logs defined on the logging subsystem. There has been some discussion around providing a better log viewer which can filter data resulting in requiring some kind of structured data. I assume there will be users wanting to view all these logs through the log viewer. Especially in a containerized environment. It really does seem we need to move to some kind of global solution. We should also consider users attempting to use log aggregation like loggly or the ELK stack. Having to make configuration changes in several places if you want to push logs somewhere isn't really ideal. was (Author: jamezp): Just adding my same comment here as this would likely be looked at first when the work starts. {quote} One thing we should start to consider is where/how these will be configured. Currently management access logs are configured under {{/core-service=management/access=audit}} and web access logging is configured under {{/subsystem=undertow/server=default-server/host=default-host/setting=access-log}}. The resources also have different models, log to different locations, etc. We should consider whether there should be a central place these can be configured or not. {quote} To follow up on that too there is currently a log viewer that can view the plain text versions of only the logs defined on the logging subsystem. There has been some discussion around providing a better log viewer which can filter data resulting in requiring some kind of structured data. I assume there will be users wanting to view all these logs through the log viewer. Especially in a containerized environment. It really does seem we need to move to some kind of global solution. > 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-607) Release WildFly Elytron 1.1.0.Beta7

by Darran Lofthouse (JIRA)

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

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-608) Upgrade to wildfly-client-config 1.0.0.Beta1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-608?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-608. ---------------------------------- Resolution: Done > Upgrade to wildfly-client-config 1.0.0.Beta1 > -------------------------------------------- > > Key: ELY-608 > URL: https://issues.jboss.org/browse/ELY-608 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta7 > > -- 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 James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-6892?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-6892: ------------------------------------- Just adding my same comment here as this would likely be looked at first when the work starts. {quote} One thing we should start to consider is where/how these will be configured. Currently management access logs are configured under {{/core-service=management/access=audit}} and web access logging is configured under {{/subsystem=undertow/server=default-server/host=default-host/setting=access-log}}. The resources also have different models, log to different locations, etc. We should consider whether there should be a central place these can be configured or not. {quote} To follow up on that too there is currently a log viewer that can view the plain text versions of only the logs defined on the logging subsystem. There has been some discussion around providing a better log viewer which can filter data resulting in requiring some kind of structured data. I assume there will be users wanting to view all these logs through the log viewer. Especially in a containerized environment. It really does seem we need to move to some kind of global solution. > 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] (WFCORE-1592) PropertiesFileLoader persists entries after deletion

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1592?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1592: ------------------------------------------ +1. If there are any issues we have time to correct them for 2.2.0.Final. > 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

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