December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-838) Ability to obtain SecurityIdentity without requiring LoginPermission

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-838?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-838: --------------------------------- You should be able to do this via: {code} newIdentity = domain.getAnonymousIdentity().createRunAsIdentity(name, false); {code} The "false" flag disables the auth check. You do need a secmgr permission to do this though (obviously). > Ability to obtain SecurityIdentity without requiring LoginPermission > -------------------------------------------------------------------- > > Key: ELY-838 > URL: https://issues.jboss.org/browse/ELY-838 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta18 > > > Integrations such as the batch subsystem within WildFly have the requirement to re-create a previous SecurityIdentity by name using their referenced SecurityDomain, however as this identity may have been inflowed the LoginPermission can not be assumed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-838) Ability to obtain SecurityIdentity without requiring LoginPermission

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-838: ------------------------------------ Summary: Ability to obtain SecurityIdentity without requiring LoginPermission Key: ELY-838 URL: https://issues.jboss.org/browse/ELY-838 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: Darran Lofthouse Priority: Critical Fix For: 1.1.0.Beta18 Integrations such as the batch subsystem within WildFly have the requirement to re-create a previous SecurityIdentity by name using their referenced SecurityDomain, however as this identity may have been inflowed the LoginPermission can not be assumed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

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

by David Lloyd (JIRA)

David Lloyd created ELY-837: ------------------------------- Summary: 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, 4 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-124) Ability to provide exception producer

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-124: ----------------------------------- Summary: Ability to provide exception producer Key: LOGTOOL-124 URL: https://issues.jboss.org/browse/LOGTOOL-124 Project: Log Tool Issue Type: Feature Request Reporter: David Lloyd Priority: Minor Sometimes you must use the same exception message for many different types of exception. It would be nice if you could give a parameter which can produce an exception, like this: {code} public interface MyLogs { // ... @Message(id = 1234, "The operation failed due to %s") <T extends Throwable> T operationFailed(@Producer Function<String, T> fn, String thing); } {code} And later at usage: {code} // ... throw MyLogs.log.operationFailed(IOException::new, "thingy"); {code} A valid function parameter must return a type which is equal or assignable to the return type, and is assignable to Throwable. Other than that, it can be treated the same as as if you were dealing with a constructor class that has exactly one constructor, using the same matching/inference logic, meaning you could also accept BiFunction which accepts two arguments. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7528) Infinispan subsystem remove operation must require reload

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7528?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7528: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9371, https://github.com/wildfly/wildfly/pull/9491 (was: https://github.com/wildfly/wildfly/pull/9371) > Infinispan subsystem remove operation must require reload > --------------------------------------------------------- > > Key: WFLY-7528 > URL: https://issues.jboss.org/browse/WFLY-7528 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7529) Singleton subsystem remove operation must require reload

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7529?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7529: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9371, https://github.com/wildfly/wildfly/pull/9491 (was: https://github.com/wildfly/wildfly/pull/9371) > Singleton subsystem remove operation must require reload > -------------------------------------------------------- > > Key: WFLY-7529 > URL: https://issues.jboss.org/browse/WFLY-7529 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Alpha1 > > > Since the add operation registers deployment unit processors, the remove operation must require a server reload. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2147) Replace AtomicLong with LongAdder

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2147?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2147: --------------------------- Description: Replace when adding simple stats. Can _not_ replace when used as a monotonic counter! > Replace AtomicLong with LongAdder > --------------------------------- > > Key: JGRP-2147 > URL: https://issues.jboss.org/browse/JGRP-2147 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > Replace when adding simple stats. Can _not_ replace when used as a monotonic counter! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2123) node path not properly completed in some commands

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2123: -------------------------------------------- Summary: node path not properly completed in some commands Key: WFCORE-2123 URL: https://issues.jboss.org/browse/WFCORE-2123 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise /deployment- is not properly completed for ls,cd,read-attribute and read-operation. That is due to an invalid completer that does validate the content of the path when parsing it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4211) MBean implementation lifecycle methods in MSC threads

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4211?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4211: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1401637|https://bugzilla.redhat.com/show_bug.cgi?id=1401637] from MODIFIED to ON_QA > MBean implementation lifecycle methods in MSC threads > ----------------------------------------------------- > > Key: WFLY-4211 > URL: https://issues.jboss.org/browse/WFLY-4211 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 9.0.0.Alpha1 > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Beta1 > > > MBean lifecycle methods should not be invoked from MSC threads, the implementation of these may block the thread, for instance due to a JNDI bind. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2147) Replace AtomicLong with LongAdder

by Bela Ban (JIRA)

Bela Ban created JGRP-2147: ------------------------------ Summary: Replace AtomicLong with LongAdder Key: JGRP-2147 URL: https://issues.jboss.org/browse/JGRP-2147 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 4.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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