July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1624) Web Console: SecurityContext facilities and integration with the core framework

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1624?page=com.atlassian.jira.plugin.... ] Heiko Braun edited comment on WFLY-1624 at 7/4/13 9:15 AM: ----------------------------------------------------------- - security context lifecylce is maintained by the place manager was (Author: heiko.braun): - secuirty context lifecylce is maintained by the place manager > Web Console: SecurityContext facilities and integration with the core framework > ------------------------------------------------------------------------------- > > Key: WFLY-1624 > URL: https://issues.jboss.org/browse/WFLY-1624 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > > We need: > - service that provides the security context per place > - gate keeper implementation that creates the security context (or rejects access) > - API for declaring security related meta data (@AccessControl(resources=[<address,...>])) used with presenter declarations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1624) Web Console: SecurityContext facilities and integration with the core framework

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1624?page=com.atlassian.jira.plugin.... ] Heiko Braun resolved WFLY-1624. ------------------------------- Labels: rbac (was: ) Fix Version/s: 8.0.0.Beta1 Resolution: Done > Web Console: SecurityContext facilities and integration with the core framework > ------------------------------------------------------------------------------- > > Key: WFLY-1624 > URL: https://issues.jboss.org/browse/WFLY-1624 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: rbac > Fix For: 8.0.0.Beta1 > > > We need: > - service that provides the security context per place > - gate keeper implementation that creates the security context (or rejects access) > - API for declaring security related meta data (@AccessControl(resources=[<address,...>])) used with presenter declarations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1624) Web Console: SecurityContext facilities and integration with the core framework

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1624?page=com.atlassian.jira.plugin.... ] Heiko Braun commented on WFLY-1624: ----------------------------------- - secuirty context lifecylce is maintained by the place manager > Web Console: SecurityContext facilities and integration with the core framework > ------------------------------------------------------------------------------- > > Key: WFLY-1624 > URL: https://issues.jboss.org/browse/WFLY-1624 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > > We need: > - service that provides the security context per place > - gate keeper implementation that creates the security context (or rejects access) > - API for declaring security related meta data (@AccessControl(resources=[<address,...>])) used with presenter declarations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1624) Web Console: SecurityContext facilities and integration with the core framework

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1624?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-1624: ------------------------------ Description: We need: - service that provides the security context per place - gate keeper implementation that creates the security context (or rejects access) - API for declaring security related meta data (@AccessControl(resources=[<address,...>])) used with presenter declarations was: We need: - service that provides the security context per place - gate keeper implementation that creates the security context (or rejects access) - API for declaring security related meta data (@RequiredResources([<address,...>])) used with presenter declarations > Web Console: SecurityContext facilities and integration with the core framework > ------------------------------------------------------------------------------- > > Key: WFLY-1624 > URL: https://issues.jboss.org/browse/WFLY-1624 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > > We need: > - service that provides the security context per place > - gate keeper implementation that creates the security context (or rejects access) > - API for declaring security related meta data (@AccessControl(resources=[<address,...>])) used with presenter declarations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1636) Children coming from a ManagementResourceRegistration.registerOverrideModel() override incorrectly appear as attributes in read-resource-description

by Kabir Khan (JIRA)

Kabir Khan created WFLY-1636: -------------------------------- Summary: Children coming from a ManagementResourceRegistration.registerOverrideModel() override incorrectly appear as attributes in read-resource-description Key: WFLY-1636 URL: https://issues.jboss.org/browse/WFLY-1636 Project: WildFly Issue Type: Bug Components: Domain Management Affects Versions: 8.0.0.Alpha2 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Alpha3 The problem is in OverrideDescriptionCombiner adding the overridden children to the attributes rather than to the children. For background, this was my initial mail on the subject. ------- I found this when trying to read the role based access control settings for the whole of WIldFly. I have worked around this with a hack on my https://github.com/kabir/wildfly/commits/rbac-play branch, which is called "Temp commit, work around problems in /subsystem=datasources/data-source=* definition of statistics". The underlying problem seems to be that there is a problem with the resource definition for this attribute/child type. Apart from this there are no other problems when running with standalone-full-ha.xml. The 'statistics' appears as an attribute when doing a read-resource-description [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:read-resource-description { "outcome" => "success", "result" => { "description" => "A JDBC data-source configuration", "attributes" => { "share-prepared-statements" => { "type" => BOOLEAN, "description" => "Whether to share prepared statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement", "expressions-allowed" => true, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, -- SNIP "statistics" => { "description" => "Runtime statistics provided by the resource adapter.", "access-type" => "read-only", "storage" => "configuration" } }, "operations" => undefined, "children" => {"connection-properties" => { "description" => "The connection-properties element allows you to pass in arbitrary connection properties to the Driver.connect(url, props) method", "model-description" => undefined }} } } However, it does not appears as a child but not as an attribute: [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:read-children-names(child-type=statistics) { "outcome" => "success", "result" => [ "jdbc", "pool" ] }[standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=statistics) { "outcome" => "failed", "failure-description" => "JBAS014640: 'statistics' is a registered child of resource ([ (\"subsystem\" => \"datasources\"), (\"data-source\" => \"ExampleDS\") ])", "rolled-back" => true } In read-resource it appears as a child: [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS:read-resource(recursive=true, include-runtime=true) { "outcome" => "success", "result" => { ---- SNIP ---- "statistics" => { "jdbc" => { "PreparedStatementCacheAccessCount" => "0", "PreparedStatementCacheAddCount" => "0", "PreparedStatementCacheCurrentSize" => "0", "PreparedStatementCacheDeleteCount" => "0", "PreparedStatementCacheHitCount" => "0", "PreparedStatementCacheMissCount" => "0" }, "pool" => { "ActiveCount" => "0", "AvailableCount" => "20", "AverageBlockingTime" => "0", "AverageCreationTime" => "0", "CreatedCount" => "0", "DestroyedCount" => "0", "InUseCount" => "0", "MaxCreationTime" => "0", "MaxUsedCount" => "0", "MaxWaitCount" => "0", "MaxWaitTime" => "0", "TimedOut" => "0", "TotalBlockingTime" => "0", "TotalCreationTime" => "0" } } } } [standalone@localhost:9990 /] /subsystem=datasources/data-source=ExampleDS/statistics=jdbc:read-resource(include-runtime=true) { "outcome" => "success", "result" => { "PreparedStatementCacheAccessCount" => "0", "PreparedStatementCacheAddCount" => "0", "PreparedStatementCacheCurrentSize" => "0", "PreparedStatementCacheDeleteCount" => "0", "PreparedStatementCacheHitCount" => "0", "PreparedStatementCacheMissCount" => "0" } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-28) ejb timer service creates empty directories for all ejbs including those without timers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-28?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-28: --------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 910193|https://bugzilla.redhat.com/show_bug.cgi?id=910193] from POST to MODIFIED > ejb timer service creates empty directories for all ejbs including those without timers > --------------------------------------------------------------------------------------- > > Key: WFLY-28 > URL: https://issues.jboss.org/browse/WFLY-28 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Priority: Minor > Labels: directory, ejb, timer > Fix For: 8.0.0.Alpha1 > > > ejb timer service creates empty directories for all ejbs include those without timers > Empty directories are being created for all ejbs, even those that do not use timers. > $JBOSS_HOME/.../data/timer-service-data/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1329) 'whoami' operation unexpectedly requires the domain wide configuration lock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1329?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1329: ----------------------------------------------- pkremens(a)redhat.com changed the Status of [bug 960497|https://bugzilla.redhat.com/show_bug.cgi?id=960497] from ON_QA to VERIFIED > 'whoami' operation unexpectedly requires the domain wide configuration lock > --------------------------------------------------------------------------- > > Key: WFLY-1329 > URL: https://issues.jboss.org/browse/WFLY-1329 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: 7.2.0.Final (EAP 6.1.0.Beta1) > Reporter: Osamu Nagano > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha2 > > Attachments: slowdeployweb.war > > > 'whoami' operation in domain mode seems to require the domain wide configuration lock. This is problematic when there is an editing operation of domain.xml like a long running undeployment because all 'whoami' requests are blocked by the existing task. The number of blocked thread increases indefinitely and it will cause an OutOfMemoryError. > It doesn't happen in standalone mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1329) 'whoami' operation unexpectedly requires the domain wide configuration lock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1329?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1329: ----------------------------------------------- pkremens(a)redhat.com made a comment on [bug 960497|https://bugzilla.redhat.com/show_bug.cgi?id=960497] Verified on EAP 6.1.1 ER2 > 'whoami' operation unexpectedly requires the domain wide configuration lock > --------------------------------------------------------------------------- > > Key: WFLY-1329 > URL: https://issues.jboss.org/browse/WFLY-1329 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: 7.2.0.Final (EAP 6.1.0.Beta1) > Reporter: Osamu Nagano > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha2 > > Attachments: slowdeployweb.war > > > 'whoami' operation in domain mode seems to require the domain wide configuration lock. This is problematic when there is an editing operation of domain.xml like a long running undeployment because all 'whoami' requests are blocked by the existing task. The number of blocked thread increases indefinitely and it will cause an OutOfMemoryError. > It doesn't happen in standalone mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1053) ResourceAdapter instances not registered for inflow crash recovery

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1053?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1053: ------------------------------------------------ Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 980920|https://bugzilla.redhat.com/show_bug.cgi?id=980920] Fix seems to be available - JBJCA-1053 > ResourceAdapter instances not registered for inflow crash recovery > ------------------------------------------------------------------ > > Key: JBJCA-1053 > URL: https://issues.jboss.org/browse/JBJCA-1053 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.17.Final, 1.1.0.Beta5 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.18.Final, 1.1.0.CR1 > > > We need to register the ResourceAdapter instances for inflow crash recovery, since we can't depend on users of ResourceAdapterRepository does it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-14: --------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug 948900|https://bugzilla.redhat.com/show_bug.cgi?id=948900] from ON_QA to VERIFIED > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 2013