December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7808) Security subsystem, audit provider-module lacks "module" attribute

by Peter Palaga (JIRA)

Peter Palaga created WFLY-7808: ---------------------------------- Summary: Security subsystem, audit provider-module lacks "module" attribute Key: WFLY-7808 URL: https://issues.jboss.org/browse/WFLY-7808 Project: WildFly Issue Type: Bug Components: Security Reporter: Peter Palaga Assignee: Darran Lofthouse Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1392436 : When adding a provider module for auditing: {code} [standalone@orac.usersys.redhat.com:9999 /] /subsystem=security/security-domain=LdapRealm/audit=classic/provider-module=test:add( => hit TAB code= module-options= {code} There is no attribute "module" which would allow a customer to install a custom module. Workaround: custom jar file must be added to the "org.picketbox" module. However, this needs to be checked/redone each time a CP is installed making it a big overhead when a customer has many installations. Logging as a bug and not an RFE, as the presence of the "module" attribute was expected. The "module" attribute is defined in the jboss-as-security and wildfly-security schemas since version 1.1, but it seems to never have been implemented. cc [~tfonteyn], [~j_ri] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2105) Raise log level of deprecations to WARN

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2105?page=com.atlassian.jira.plugi... ] Philippe Marschall closed WFCORE-2105. -------------------------------------- Resolution: Rejected INFO is fine > Raise log level of deprecations to WARN > --------------------------------------- > > Key: WFCORE-2105 > URL: https://issues.jboss.org/browse/WFCORE-2105 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Philippe Marschall > > We believe the log level of log level of deprecations should be WARN > instead of INFO. We were using a deprecated attribute and almost didn't > see the message in the see of INFO messages. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4407) Upgrade wildfly-core to 1.0.0.Beta1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4407?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4407: ----------------------------------------------- Miroslav Sochurek <msochure(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from POST to MODIFIED > Upgrade wildfly-core to 1.0.0.Beta1 > ----------------------------------- > > Key: WFLY-4407 > URL: https://issues.jboss.org/browse/WFLY-4407 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond

by Christian Bjørnbak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ] Christian Bjørnbak commented on WFLY-7275: ------------------------------------------ [~lafr] I see your point but thanks for your pointers to a solution! > Wildfly eats the CPU up to 100% and does not respond > ---------------------------------------------------- > > Key: WFLY-7275 > URL: https://issues.jboss.org/browse/WFLY-7275 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit > Reporter: Krisztian Kocsis > Assignee: Stuart Douglas > Fix For: 11.0.0.Alpha1 > > Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang-real-stacktrace.txt, wildfly-hang.txt > > > Hi! > > I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server. > It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile. > > I'v attached the stack trace but I unfortunately don't see anything according to my knowledge. > Please help me, I can provide more information if necessary. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-837) Clean up provider usage and definition in XML config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-837?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-837: -------------------------------------- ELY-840 starts to make it possible to use Providers discovered later within the configuration, this should be extended to provider discovery is at the metaphorical root of configuration and then children can have a provider-name attribute to filter by name. > Clean up provider usage and definition in XML config > ---------------------------------------------------- > > Key: ELY-837 > URL: https://issues.jboss.org/browse/ELY-837 > Project: WildFly Elytron > Issue Type: Task > Components: XML > Reporter: David Lloyd > Priority: Critical > > We are very inconsistent about how we're defining and using providers in the XML configuration. We need to meet the following requirements: > * Provide a single top-level element from the substitution group {{abstract-providers}} that specifies the providers to use in the absence of any other configuration; default to {{use-system-providers}} > * Update the following types (or appropriate enclosing type) to accept an optional nested {{abstract-providers}} override: > ** {{key-store-type}} > ** {{credential-store-type}} > ** {{hashed-password-type}} > * Update the following types to use an optional {{provider}} *attribute* (not nested element) to allow selection of a specific provider: > ** {{credential-store-type}} > ** {{key-store-type}} -- already done! > ** {{hashed-password-type}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-840) Ensure configured Providers are used for PasswordFactory interaction.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-840?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-840: --------------------------------- Summary: Ensure configured Providers are used for PasswordFactory interaction. (was: Allow for creation of CredentialSource to be delayed until for specific AuthenticationConfiguration instance.) > Ensure configured Providers are used for PasswordFactory interaction. > --------------------------------------------------------------------- > > Key: ELY-840 > URL: https://issues.jboss.org/browse/ELY-840 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta18 > > > This should also allow for the Providers[] from the AuthenticationConfiguration to be used for any deferred initialisation of the CredentialSource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-840) Ensure configured Providers are used for PasswordFactory interaction.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-840?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-840: --------------------------------- Description: (was: This should also allow for the Providers[] from the AuthenticationConfiguration to be used for any deferred initialisation of the CredentialSource.) > Ensure configured Providers are used for PasswordFactory interaction. > --------------------------------------------------------------------- > > Key: ELY-840 > URL: https://issues.jboss.org/browse/ELY-840 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta18 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7275) Wildfly eats the CPU up to 100% and does not respond

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-7275?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-7275: --------------------------------------- In general I agree with you, I also would like to see public patches for the open source releases. But it's also understandable, that JBoss / RedHat as a commercial company has to earn money. So you might have a look at the commercial JBoss version, the Enterprise Application Platform. Otherwise you can hot fix your current version: - Download xnio-nio-3.4.x.Final.jar and xnio-api-3.4.x.Final.jar (x >= 1) - put these files into the folders $JBOSS_HOME/modules/system/layers/base/org/jboss/xnio/main and $JBOSS_HOME/modules/system/layers/base/org/jboss/xnio/nio/main - modify module.xml in both directories to load the new version of the files instead of 3.4.0. Restart JBoss. > Wildfly eats the CPU up to 100% and does not respond > ---------------------------------------------------- > > Key: WFLY-7275 > URL: https://issues.jboss.org/browse/WFLY-7275 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: Ubuntu 14.04, Linux 3.19, Oracle Java 8u91 64-bit > Reporter: Krisztian Kocsis > Assignee: Stuart Douglas > Fix For: 11.0.0.Alpha1 > > Attachments: Screen Shot 2016-10-07 at 20.18.27.png, Screen Shot 2016-10-07 at 20.18.31.png, wildfly-after-hang+1min.txt, wildfly-after-hang.txt, wildfly-hang-real-stacktrace.txt, wildfly-hang.txt > > > Hi! > > I have a JAX-RS application and after a lot of load, one thread eats up the CPU (100% usage) even when the load test app is terminated, and never drops down until I restart the app server. > It causes me a lot of headeches because it totally makes the app server unusable until I restart, but the users unable to use the app in the meanwhile. > > I'v attached the stack trace but I unfortunately don't see anything according to my knowledge. > Please help me, I can provide more information if necessary. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-840) Allow for creation of CredentialSource to be delayed until for specific AuthenticationConfiguration instance.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-840: ------------------------------------ Summary: Allow for creation of CredentialSource to be delayed until for specific AuthenticationConfiguration instance. Key: ELY-840 URL: https://issues.jboss.org/browse/ELY-840 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta18 This should also allow for the Providers[] from the AuthenticationConfiguration to be used for any deferred initialisation of the CredentialSource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-839) SetCredentialsConfiguration not overriding getCredentialSource()

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-839: ------------------------------------ Summary: SetCredentialsConfiguration not overriding getCredentialSource() Key: ELY-839 URL: https://issues.jboss.org/browse/ELY-839 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Various methods manipulating the CredentialSource attempt to obtain the current one to add to it but as it is never returned they would always use the default one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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