August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3085) Update license related information

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3085?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3085: ------------------------------------- Fix Version/s: 3.0.0.CR1 (was: 3.0.0.Beta29) > Update license related information > ---------------------------------- > > Key: WFCORE-3085 > URL: https://issues.jboss.org/browse/WFCORE-3085 > Project: WildFly Core > Issue Type: Task > Affects Versions: 3.0.0.Beta28 > Reporter: Petr Sakař > Assignee: Brian Stansberry > Fix For: 3.0.0.CR1 > > > Please change name of license in root pom file licenses tag to comply with the name from the first column of the license list https://spdx.org/licenses/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-154) Bring dependencies to Final versions aligned with WildFly Core

by Brian Stansberry (JIRA)

Brian Stansberry created REMJMX-154: --------------------------------------- Summary: Bring dependencies to Final versions aligned with WildFly Core Key: REMJMX-154 URL: https://issues.jboss.org/browse/REMJMX-154 Project: Remoting JMX Issue Type: Task Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 3.0.0.CR2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3155) Upgrade to jboss-remoting 5.0.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3155?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3155: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Upgrade to jboss-remoting 5.0.0.Final > ------------------------------------- > > Key: WFCORE-3155 > URL: https://issues.jboss.org/browse/WFCORE-3155 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3155) Upgrade to jboss-remoting 5.0.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3155?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3155: ---------------------------------------- Assignee: Brian Stansberry (was: David Lloyd) > Upgrade to jboss-remoting 5.0.0.Final > ------------------------------------- > > Key: WFCORE-3155 > URL: https://issues.jboss.org/browse/WFCORE-3155 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3155) Upgrade to jboss-remoting 5.0.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3155?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3155: ------------------------------------- Priority: Blocker (was: Major) > Upgrade to jboss-remoting 5.0.0.Final > ------------------------------------- > > Key: WFCORE-3155 > URL: https://issues.jboss.org/browse/WFCORE-3155 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3152) Upgrade to jboss-invocation 1.5.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3152?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3152: ---------------------------------------- Assignee: Brian Stansberry (was: David Lloyd) > Upgrade to jboss-invocation 1.5.0.Final > --------------------------------------- > > Key: WFCORE-3152 > URL: https://issues.jboss.org/browse/WFCORE-3152 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Kabir Khan > Assignee: Brian Stansberry > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3152) Upgrade to jboss-invocation 1.5.0.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3152?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3152: ------------------------------------- Priority: Blocker (was: Major) > Upgrade to jboss-invocation 1.5.0.Final > --------------------------------------- > > Key: WFCORE-3152 > URL: https://issues.jboss.org/browse/WFCORE-3152 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Kabir Khan > Assignee: David Lloyd > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-609) Unguarded read in ElytronPolicyConfiguration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-609?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-609: ------------------------------------ Assignee: (was: Darran Lofthouse) > Unguarded read in ElytronPolicyConfiguration > -------------------------------------------- > > Key: ELY-609 > URL: https://issues.jboss.org/browse/ELY-609 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta7 > Reporter: Ondrej Lukas > Labels: static_analysis > Fix For: 1.2.0.Beta1 > > > Access to fields {{uncheckedPermissions}}, {{excludedPermissions}} and {{rolePermissions}} in {{org.wildfly.security.authz.jacc.ElytronPolicyConfiguration}} is holded by lock. However lock is not used in their getter methods. Getters should be also handled by locks to avoid unguarded read of those fields. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-735) Remove PeerIdentity bundling from SecurityIdentity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-735?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-735: ------------------------------------ Assignee: (was: David Lloyd) > Remove PeerIdentity bundling from SecurityIdentity > -------------------------------------------------- > > Key: ELY-735 > URL: https://issues.jboss.org/browse/ELY-735 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: David Lloyd > > The primary use case of the PeerIdentitys-inside-SecurityIdentity bundling capability is bundling a Subject with the SI. But, the PI mechanism can't encompass Subject because of the way Subject.doAs works versus PI's pre/postAssociate mechanism. > If we do need the Subject bundling capability, we should just add a Subject field to SI and a method to create a bundled SI. > SI is in fact more closely aligned with an "SI is-a PI" arrangement, which we might or might not want to pursue later. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1024) Match rules do not allow matching any-or-no user

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1024?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1024: ------------------------------------- Assignee: (was: David Lloyd) > Match rules do not allow matching any-or-no user > ------------------------------------------------ > > Key: ELY-1024 > URL: https://issues.jboss.org/browse/ELY-1024 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 August 2017