September 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-650) Improvements to elytron-web testsuite

by Pedro Igor (JIRA)

Pedro Igor created ELY-650: ------------------------------ Summary: Improvements to elytron-web testsuite Key: ELY-650 URL: https://issues.jboss.org/browse/ELY-650 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Affects Versions: 1.1.0.Beta10 Reporter: Pedro Igor Assignee: Darran Lofthouse Fix For: 1.1.0.Beta11 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-650) Improvements to elytron-web testsuite

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-650?page=com.atlassian.jira.plugin.sy... ] Pedro Igor reassigned ELY-650: ------------------------------ Assignee: Pedro Igor (was: Darran Lofthouse) > Improvements to elytron-web testsuite > ------------------------------------- > > Key: ELY-650 > URL: https://issues.jboss.org/browse/ELY-650 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.1.0.Beta10 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta11 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1842) Support RBAC based on raw roles from an Identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1842?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1842: ------------------------------------------ +1 we removed useRealmRoles as it was confusing in the context of the legacy security realms - now the roles are available from an Elytron SecurityIdentity making it possible to enable a default 1:1 mapping makes sense again. > Support RBAC based on raw roles from an Identity > ------------------------------------------------- > > Key: WFCORE-1842 > URL: https://issues.jboss.org/browse/WFCORE-1842 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Pedro Igor > Assignee: Darran Lofthouse > > Currently, RBAC requires a static mapping between standard roles and raw roles from an identity. > We should be able to use RBAC without necessarily forcing this static mapping and just consider the raw roles from the identity. > This issue may be related with exposing {{org.jboss.as.controller.access.management.WritableAuthorizerConfiguration#useRealmRoles}} in the management model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1842) Support RBAC based on raw roles from an Identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1842?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-1842: ---------------------------------------- Assignee: Darran Lofthouse > Support RBAC based on raw roles from an Identity > ------------------------------------------------- > > Key: WFCORE-1842 > URL: https://issues.jboss.org/browse/WFCORE-1842 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Pedro Igor > Assignee: Darran Lofthouse > > Currently, RBAC requires a static mapping between standard roles and raw roles from an identity. > We should be able to use RBAC without necessarily forcing this static mapping and just consider the raw roles from the identity. > This issue may be related with exposing {{org.jboss.as.controller.access.management.WritableAuthorizerConfiguration#useRealmRoles}} in the management model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-482: -------------------------------------- This is something I've started working on. Currently I'm just implementing a log4j2 {{LoggerContextFactory}} which uses a {{org.jboss.logmanager.Logger}}. If anyone has some example uses cases of how they use log4j2 that would be helpful. Some questions that would be helpful to know the answer to: # Do you just use the log4j2-api? # Do you use a custom {{LoggerContextFactory}}? # Are you using system properties or a properties file to configure log4j2? # Are you using the log4j-web dependency? Any other comments on how you're using log4j2 in WildFly or any container would be helpful. Thanks in advance! > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.jboss.org/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Optional > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1313) Memory Leak - but is this a supported scenario for Dynamic rule management

by Bill Tuminaro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1313?page=com.atlassian.jira.plugi... ] Bill Tuminaro commented on DROOLS-1313: --------------------------------------- I added some System.gc() calls after the updateToVersion() calls, they do not seem to have any affect. > Memory Leak - but is this a supported scenario for Dynamic rule management > -------------------------------------------------------------------------- > > Key: DROOLS-1313 > URL: https://issues.jboss.org/browse/DROOLS-1313 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Bill Tuminaro > Assignee: Mario Fusco > Attachments: SAVE_SimpleTest.java, SAVE_SimpleTest2.java, SimpleTest2_dump1.PNG, SimpleTest2_dump2.PNG, SimpleTest2_dump3.PNG, SimpleTestDump1.PNG, SimpleTestDump2.PNG, SimpleTestDump3.PNG > > > I have a reproducer that shows a clear memory leak based on heap dumps created and reviewing them with the Eclipse Memory Analyzer tool (http://www.eclipse.org/mat/). > However, I am not sure this is a supported scenario. If this is a supported approach this needs to get fixed, otherwise we need to use another approach. > The attached source does this: > +*Initialize stuff*+ > - Create a new ReleaseId > - Create a new KieFileSystem > - Generate and write the PomXML for the ReleaseId created above > - Create a new KieModuleModel > - Create a new KieBaseModel > - Write the ModuleModel XML to the KieFileSystem > - Write 2 rules into the KieFileSystem > +*1st build and dump*+ > - Create a new KieBuilder > - Do a buildall() with the KieBuilder > - Create a new KieContainer > - Create a new KieSession from the KieContainer > - Print out the rules in the KieContainer for the package used in my rules > - Create a java heap dump (SimpleTestFirstDump.dmp), see SimpleTestDump1.png as you can see we have 2 classloaders for each class created for these rules. This is not the leak, yet, just curious if this is expected. > +*2nd build and dump*+ > - Delete 2 rules from the KieFileSystem created above > - Call incrementalBuild() on the KieBuilder created above > - Call updateToVersion() on the KieContaincer created above, using the SAME ReleaseID created above > - Add 2 new rules to the KieFileSystem created above > - Call incrementalBuild() on the KieBuilder created above > - Call updateToVersion() on the KieContaincer created above, using the SAME ReleaseID created above > - Print out the rules in the KieContainer for the package used in my rules > - Create a java heap dump (SimpleTestSecondDump.dmp), see SimpleTestDump2.png. > - Rule_120_Triggered_Part_1_ 0 is not there > - Another class loader and instances of Rule_Internal_rule_0_DefaultConsequenceInvoker is present ( I think this is the leak) > +*3rd build and dump*+ > - Delete 1 rule from the KieFileSystem created above > - Call incrementalBuild() on the KieBuilder created above > - Call updateToVersion() on the KieContaincer created above, using the SAME ReleaseID created above > - Add 2 new rules to the KieFileSystem created above > - Call incrementalBuild() on the KieBuilder created above > - Call updateToVersion() on the KieContaincer created above, using the SAME ReleaseID created above > - Print out the rules in the KieContainer for the package used in my rules > - Create a java heap dump (SimpleTestThirdDump.dmp), see SimpleTestDump3.png. > - Rule_120_Triggered_Part_1_ 0 is STILL not there > - TWO more class loaders and instances of Rule_Internal_rule_0_DefaultConsequenceInvoker is present ( I think this is the leak) > - Another class loader and instances of Rule_120_Triggered_part_10DefaultConsequenceInvoker is present ( I think this is also part of the leak) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1842) Support RBAC based on raw roles from an Identity

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1842?page=com.atlassian.jira.plugi... ] Pedro Igor commented on WFCORE-1842: ------------------------------------ Nope. Accordingly with [~darranl], we just need to get it back and keep original behavior. > Support RBAC based on raw roles from an Identity > ------------------------------------------------- > > Key: WFCORE-1842 > URL: https://issues.jboss.org/browse/WFCORE-1842 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Pedro Igor > > Currently, RBAC requires a static mapping between standard roles and raw roles from an identity. > We should be able to use RBAC without necessarily forcing this static mapping and just consider the raw roles from the identity. > This issue may be related with exposing {{org.jboss.as.controller.access.management.WritableAuthorizerConfiguration#useRealmRoles}} in the management model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1842) Support RBAC based on raw roles from an Identity

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1842?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1842: ------------------------------------------ Is this a proposal to do anything beyond what the original useRealmRoles did? > Support RBAC based on raw roles from an Identity > ------------------------------------------------- > > Key: WFCORE-1842 > URL: https://issues.jboss.org/browse/WFCORE-1842 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Pedro Igor > > Currently, RBAC requires a static mapping between standard roles and raw roles from an identity. > We should be able to use RBAC without necessarily forcing this static mapping and just consider the raw roles from the identity. > This issue may be related with exposing {{org.jboss.as.controller.access.management.WritableAuthorizerConfiguration#useRealmRoles}} in the management model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7247) Wildfly 10 JSESSIONIDSSOs not being created

by M Wardell (JIRA)

M Wardell created WFLY-7247: ------------------------------- Summary: Wildfly 10 JSESSIONIDSSOs not being created Key: WFLY-7247 URL: https://issues.jboss.org/browse/WFLY-7247 Project: WildFly Issue Type: Bug Affects Versions: 10.1.0.Final, 10.0.0.Final Reporter: M Wardell Assignee: Jason Greene Found on wildfly 10.1 and 10.0. With SSO enabled, the server can startup in a state where not all the deployments get the SSO auth mechanism. Possibly caused by a missing dependency between the UndertowDeploymentInfoService and SingleSignOnService, which could be allowing the deployments to start before the SSO auth mechanism is registered in the host service. Issue in intermittent on startup. After most startups the JESSSIONIDSSO is reliably generated during login. After some startups the JSESSIONIDSSO is never created after login. Details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1335) Add protection in RaXmlDeployer to prevent from loading xml resource

by COLLIGNON Thomas (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1335?page=com.atlassian.jira.plugin... ] COLLIGNON Thomas commented on JBJCA-1335: ----------------------------------------- Same things here : https://issues.jboss.org/browse/JBJCA-1333 > Add protection in RaXmlDeployer to prevent from loading xml resource > -------------------------------------------------------------------- > > Key: JBJCA-1335 > URL: https://issues.jboss.org/browse/JBJCA-1335 > Project: IronJacamar > Issue Type: Enhancement > Components: Deployer > Affects Versions: 1.2.7.Final > Reporter: COLLIGNON Thomas > Priority: Minor > Fix For: 1.2.8.Final > > > If we place a -ra.xml in jar file, the class RaXmlDeployer will fail with "URI not hierarchical error", because it doesn't handle jar file. > The goal of this issue is prevent for loading jar file in RaXmlDeployer . > The second goal is to provide ability of overring RaXmlDeployer in custom deployer who extends this class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2016