December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Fix Version/s: 1.1.0.Beta19 (was: 1.1.0.Beta18) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta19 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-835: --------------------------------- Fix Version/s: 1.1.0.Beta19 (was: 1.1.0.Beta18) > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta19 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-823) Constructor JaccDelegatingPolicy(Policy) not initializing supported permissions

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-823?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-823: --------------------------------- Fix Version/s: 1.1.0.Beta19 (was: 1.1.0.Beta18) > Constructor JaccDelegatingPolicy(Policy) not initializing supported permissions > ------------------------------------------------------------------------------- > > Key: ELY-823 > URL: https://issues.jboss.org/browse/ELY-823 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Affects Versions: 1.1.0.Beta16 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta19 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-851) Release WildFly Elytron 1.1.0.Beta18

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-851?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-851. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta18 > ------------------------------------ > > Key: ELY-851 > URL: https://issues.jboss.org/browse/ELY-851 > Project: WildFly Elytron > Issue Type: Release > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7818) Upgrade to Elytron Subsystem 1.0.0.Alpha17

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-7818: -------------------------------------- Summary: Upgrade to Elytron Subsystem 1.0.0.Alpha17 Key: WFLY-7818 URL: https://issues.jboss.org/browse/WFLY-7818 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2130) Upgrade to Elytron Web 1.0.0.Beta7

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2130: ---------------------------------------- Summary: Upgrade to Elytron Web 1.0.0.Beta7 Key: WFCORE-2130 URL: https://issues.jboss.org/browse/WFCORE-2130 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha16 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2129) Upgrade to WildFly Elytron 1.1.0.Beta18

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2129: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta18 Key: WFCORE-2129 URL: https://issues.jboss.org/browse/WFCORE-2129 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha16 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6215) SessionSynchronization callbacks allow concurrent access to SFSB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6215?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6215: ----------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1308993|https://bugzilla.redhat.com/show_bug.cgi?id=1308993] from ASSIGNED to CLOSED > SessionSynchronization callbacks allow concurrent access to SFSB > ---------------------------------------------------------------- > > Key: WFLY-6215 > URL: https://issues.jboss.org/browse/WFLY-6215 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Ryan Emerson > Assignee: Stuart Douglas > Priority: Critical > Labels: downstream_dependency > Fix For: 10.1.0.CR1, 10.1.0.Final > > Attachments: wfly_reproducer.tar.gz > > > Issue first encountered by customer in EAP5 (JBPAPP-11239). > Assume a local SFSB, B1, with container managed transactions and a calling SFSB, B2, which has bean managed transactions. B1 implements the SessionSynchronization interface. > When B2's bean managed transaction timesout whilst executing B1.exampleMethod(), B2's transaction aborts and the transaction reaper thread calls B1.afterCompletion(). However, the original worker thread that was executing B1.exampleMethod() continues to execute B1.exampleMethod() until it has completed. Hence it is possible for the B1 SFSB to be accessed concurrently. It is also possible for B1.afterCompletion() to finish executing before B1.exampleMethod(). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-851) Release WildFly Elytron 1.1.0.Beta18

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-851: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta18 Key: ELY-851 URL: https://issues.jboss.org/browse/ELY-851 Project: WildFly Elytron Issue Type: Release 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-841) Coverity static analysis: Resource leaks in ProviderLoaderService (Elytron subsystem)

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-841?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-841: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity static analysis: Resource leaks in ProviderLoaderService (Elytron subsystem) > ------------------------------------------------------------------------------------- > > Key: ELY-841 > URL: https://issues.jboss.org/browse/ELY-841 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Critical > Labels: static_analysis > > Coverity static-analysis scan found 2 resource leaks in {{ProviderLoaderService}} class. > 1) > https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... > Following code is used in `load` method: > {code:java} > if (provider == null) { > provider = providerClazz.newInstance(); > if (configurationStreamSupplier != null) { > try (InputStream is = configurationStreamSupplier.get()) { > provider.load(configurationStreamSupplier.get()); > } > } > } > {code} > The load method should use `is` instance instead of calling the supplier again. > 2) > https://scan7.coverity.com/reports.htm#v16159/p12663/fileInstanceId=68921... > Following code is used in `toInputStream` method: > {code:java} > SecurityActions.doPrivileged((PrivilegedExceptionAction<InputStream>) () -> new FileInputStream(file) ); > return new FileInputStream(file); > {code} > There should be probably just: > {code:java} > return SecurityActions.doPrivileged((PrivilegedExceptionAction<InputStream>) () -> new FileInputStream(file) ); > {code} -- 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