November 2016 - jboss-jira - Jboss List Archives

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

by David Lloyd (JIRA)

David Lloyd created ELY-735: ------------------------------- Summary: 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 Assignee: 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)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-733) Coverity static analysis: Useless call in Elytron

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-733?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-733: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity static analysis: Useless call in Elytron > ------------------------------------------------- > > Key: ELY-733 > URL: https://issues.jboss.org/browse/ELY-733 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Minor > Labels: static_analysis > > Coverity static analysis: Useless call in Elytron > Coverity static-analysis scan found useless call in the {{FileSystemSecurityRealm.writeIdentity()}} method on line 554 (currently). > There is an orphan call of {{otp.getHash()}}. > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57216... > The correct call is on the line 557, where it's used in streamWriter. > *Suggested improvement* > Remove the useless call. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5785) EJB lookup fails with "No cluster context available" in failover tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5785?page=com.atlassian.jira.plugin.... ] Radoslav Husar reopened WFLY-5785: ---------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) > EJB lookup fails with "No cluster context available" in failover tests > ---------------------------------------------------------------------- > > Key: WFLY-5785 > URL: https://issues.jboss.org/browse/WFLY-5785 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Fix For: 10.0.0.Final > > > Seen in our failover tests for remote stateful EJBs - scenarios: > ejb-ejbremote-shutdown-dist-async > ejb-ejbremote-shutdown-dist-sync > ejb-ejbremote-undeploy-dist-async > After failing a node, occasionally EJB lookup starts failing - client starts logging these error messages: > {code} > 2015/12/03 04:46:47:078 EST [ERROR][Runner - 9] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb> > java.lang.IllegalStateException: EJBCLIENT000029: No cluster context available for cluster named ejb > at org.jboss.ejb.client.EJBClientContext.requireClusterEJBReceiverContext(EJBClientContext.java:1063) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:84) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy2.getSerialAndIncrement(Unknown Source) > at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:84) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) > at java.lang.Thread.run(Thread.java:745) > {code} > It stops logging these messages only after the failed node is restarted and joins the cluster again. > Link (this job was configured to use only 100 sessions in order to keep the log size small) > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-failo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-734) Where there is no peer certificate the CLIENT-CERT authentication mechanism should not report an error.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-734?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-734: --------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/547 > Where there is no peer certificate the CLIENT-CERT authentication mechanism should not report an error. > ------------------------------------------------------------------------------------------------------- > > Key: ELY-734 > URL: https://issues.jboss.org/browse/ELY-734 > Project: WildFly Elytron > Issue Type: Release > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta14 > > > Where there is no peer certificate the CLIENT-CERT mechanism should report that there is no authentication in progress instead of throwing an Exception to give other mechanisms an opportunity to authenticate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-621) Client Cert authentication trigger SSLSession renegotiation?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-621?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-621: -------------------------------------- We will need to also ensure that renegotiation can be disabled. > Client Cert authentication trigger SSLSession renegotiation? > ------------------------------------------------------------ > > Key: ELY-621 > URL: https://issues.jboss.org/browse/ELY-621 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta14 > > > This could be an option to enable demanding client verification for an established connection but depending on the application being accessed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-621) Client Cert authentication trigger SSLSession renegotiation?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-621?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-621: --------------------------------- Fix Version/s: 1.1.0.Beta14 (was: 1.1.0.Beta15) > Client Cert authentication trigger SSLSession renegotiation? > ------------------------------------------------------------ > > Key: ELY-621 > URL: https://issues.jboss.org/browse/ELY-621 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta14 > > > This could be an option to enable demanding client verification for an established connection but depending on the application being accessed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-621) Client Cert authentication trigger SSLSession renegotiation?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-621?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-621: --------------------------------- Summary: Client Cert authentication trigger SSLSession renegotiation? (was: Can Client Cert authentication trigger SSLSession renegotiation?) > Client Cert authentication trigger SSLSession renegotiation? > ------------------------------------------------------------ > > Key: ELY-621 > URL: https://issues.jboss.org/browse/ELY-621 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > This could be an option to enable demanding client verification for an established connection but depending on the application being accessed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-734) Where there is no peer certificate the CLIENT-CERT authentication mechanism should not report an error.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-734: ------------------------------------ Summary: Where there is no peer certificate the CLIENT-CERT authentication mechanism should not report an error. Key: ELY-734 URL: https://issues.jboss.org/browse/ELY-734 Project: WildFly Elytron Issue Type: Release Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta14 Where there is no peer certificate the CLIENT-CERT mechanism should report that there is no authentication in progress instead of throwing an Exception to give other mechanisms an opportunity to authenticate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-733) Coverity static analysis: Useless call in Elytron

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-733?page=com.atlassian.jira.plugin.sy... ] Josef Cacek updated ELY-733: ---------------------------- Labels: static_analysis (was: ) > Coverity static analysis: Useless call in Elytron > ------------------------------------------------- > > Key: ELY-733 > URL: https://issues.jboss.org/browse/ELY-733 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Minor > Labels: static_analysis > > Coverity static analysis: Useless call in Elytron > Coverity static-analysis scan found useless call in the {{FileSystemSecurityRealm.writeIdentity()}} method on line 554 (currently). > There is an orphan call of {{otp.getHash()}}. > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57216... > The correct call is on the line 557, where it's used in streamWriter. > *Suggested improvement* > Remove the useless call. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-733) Coverity static analysis: Useless call in Elytron

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-733?page=com.atlassian.jira.plugin.sy... ] Josef Cacek updated ELY-733: ---------------------------- Description: Coverity static analysis: Useless call in Elytron Coverity static-analysis scan found useless call in the {{FileSystemSecurityRealm.writeIdentity()}} method on line 554 (currently). There is an orphan call of {{otp.getHash()}}. https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57216... The correct call is on the line 557, where it's used in streamWriter. *Suggested improvement* Remove the useless call. was: Coverity static analysis: Useless call in Elytron Coverity static-analysis scan found useless call in the {{FileSystemSecurityRealm.writeIdentity()}} method on line 554 (currently). There is an orphan call of {{otp.getHash()}}. https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57216... The correct call is on the line 557, where it's used in streamWriter. **Suggested improvement** Remove the useless call. > Coverity static analysis: Useless call in Elytron > ------------------------------------------------- > > Key: ELY-733 > URL: https://issues.jboss.org/browse/ELY-733 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Minor > Labels: static_analysis > > Coverity static analysis: Useless call in Elytron > Coverity static-analysis scan found useless call in the {{FileSystemSecurityRealm.writeIdentity()}} method on line 554 (currently). > There is an orphan call of {{otp.getHash()}}. > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57216... > The correct call is on the line 557, where it's used in streamWriter. > *Suggested improvement* > Remove the useless call. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016