April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Description: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- -if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } - was: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- {code:java} -if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } -{code}- > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- > -if (completed) { > throw new IllegalStateException( > "EXTERNAL supports neither integrity nor privacy"); > } else { > throw new IllegalStateException( > "Authentication not completed"); > } > - -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Description: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. -We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods: {code:java} if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } {code}- was: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods: {code:java} if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } {code} > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > -We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods: > {code:java} > if (completed) { > throw new IllegalStateException( > "EXTERNAL supports neither integrity nor privacy"); > } else { > throw new IllegalStateException( > "Authentication not completed"); > } > {code}- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8540) Former singleton provider node leaving cluster after re-election causes another re-election

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8540?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-10216 to WFLY-8540: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8540 (was: JBEAP-10216) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.DR15) > Former singleton provider node leaving cluster after re-election causes another re-election > -------------------------------------------------------------------------------------------- > > Key: WFLY-8540 > URL: https://issues.jboss.org/browse/WFLY-8540 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > With a random election policy, this situation is likely to happen: > 1. After a topology change, new singleton provider is elected > 2. Former singleton provider undeploys the singleton application, which causes it to leave a cluster for a while > 3. This topology change triggers another election > 4. Loop continues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-37) Server Group Deployment

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-37?page=com.atlassian.jira.plu... ] Prachi Yadav commented on HAWKULARQE-37: ---------------------------------------- Test case created https://github.com/Hawkular-QE/cf-ui/pull/155 > Server Group Deployment > ----------------------- > > Key: HAWKULARQE-37 > URL: https://issues.jboss.org/browse/HAWKULARQE-37 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8539) Modify 'integration/web/security/...' tests to be able to run with Elytron

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-8539?page=com.atlassian.jira.plugin.... ] Jan Stourac moved JBEAP-10215 to WFLY-8539: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8539 (was: JBEAP-10215) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.DR16) > Modify 'integration/web/security/...' tests to be able to run with Elytron > -------------------------------------------------------------------------- > > Key: WFLY-8539 > URL: https://issues.jboss.org/browse/WFLY-8539 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Jan Stourac > Assignee: Jan Stourac > > Update relevant tests in [wildfly '...integration/web/security testsuite..'|https://github.com/wildfly/wildfly/tree/master/testsuite/integration/web/src/test/java/org/jboss/as/test/integration/web/security] so they are able to run with Elytron too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2642) History and completion must be disabled when accepting server certificate

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2642: -------------------------------------------- Summary: History and completion must be disabled when accepting server certificate Key: WFCORE-2642 URL: https://issues.jboss.org/browse/WFCORE-2642 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise completion and history are enabled when prompting user for certificate acceptance. That is not the case for userName/password. Code refactoring is required to share the same logic for all these users interaction. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-983) WildFlySasl.MECHANISM_QUERY_ALL is taken into account in ExternalSasl*Factory.createSasl* methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-983?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-983: --------------------------------- Fix Version/s: 1.1.0.Beta36 > WildFlySasl.MECHANISM_QUERY_ALL is taken into account in ExternalSasl*Factory.createSasl* methods > ------------------------------------------------------------------------------------------------- > > Key: ELY-983 > URL: https://issues.jboss.org/browse/ELY-983 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta36 > > > The description of {{MECHANISM_QUERY_ALL}} filtering property says: > {quote} > This flag is only effective on calls to SaslServerFactory.getMechanismNames(Map) or SaslClientFactory.getMechanismNames(Map) for Elytron-provided SASL factories. > {quote} > It's not true for EXTERNAL SASL mechanism factories, where it's taken into account also in {{createSaslServer/Client}} methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8524) OwnableReentrantLock can't recognize two different but equal transaction objects as the same transaction

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8524?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-8524: ----------------------------------- Might also be the cause of exceptions like this: {noformat} 2017-04-07 09:47:10 Caused by: java.lang.IllegalMonitorStateException 2017-04-07 09:47:10 at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) 2017-04-07 09:47:10 at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) 2017-04-07 09:47:10 at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) 2017-04-07 09:47:10 at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.persistTimer(FileTimerPersistence.java:240) 2017-04-07 09:47:10 at org.jboss.as.ejb3.timerservice.persistence.filestore.FileTimerPersistence.addTimer(FileTimerPersistence.java:177) 2017-04-07 09:47:10 at org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:607) 2017-04-07 09:47:10 ... 70 more {noformat} > OwnableReentrantLock can't recognize two different but equal transaction objects as the same transaction > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-8524 > URL: https://issues.jboss.org/browse/WFLY-8524 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Reporter: David Lloyd > Priority: Critical > > The transaction manager is allowed to create more than one Transaction object for an imported transaction, and has been observed to do so in at least distributed JTA cases if not other cases. > The JTA specification says that the equals method must return true for two objects that refer to the same transaction. Therefore OwnableReentrantLock must use equals() on its owner argument. > As an aside, that class should probably also null-check its owner object on lock() to avoid weird states. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8530) Wrong ZonedDateTime value read when attribute annotated with @Id

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-8530?page=com.atlassian.jira.plugin.... ] Jörg Bäsner closed WFLY-8530. ----------------------------- Resolution: Duplicate This bug has been closed, as it is being replaced with the upstream bug created in the Hibernate Jira... > Wrong ZonedDateTime value read when attribute annotated with @Id > ---------------------------------------------------------------- > > Key: WFLY-8530 > URL: https://issues.jboss.org/browse/WFLY-8530 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.1.0.Final > Reporter: Jörg Bäsner > Assignee: Scott Marlow > Attachments: playground-prj.tar.gz > > > A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly. > The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows: > * with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG* > * without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8530) Wrong ZonedDateTime value read when attribute annotated with @Id

by Jörg Bäsner (JIRA)

[ https://issues.jboss.org/browse/WFLY-8530?page=com.atlassian.jira.plugin.... ] Jörg Bäsner commented on WFLY-8530: ----------------------------------- This bug has been replaced with this linked Hibernate upstream bug... > Wrong ZonedDateTime value read when attribute annotated with @Id > ---------------------------------------------------------------- > > Key: WFLY-8530 > URL: https://issues.jboss.org/browse/WFLY-8530 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.1.0.Final > Reporter: Jörg Bäsner > Assignee: Scott Marlow > Attachments: playground-prj.tar.gz > > > A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly. > The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows: > * with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG* > * without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017