April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-8485?page=com.atlassian.jira.plugin.... ] Ivo Studensky resolved WFLY-8485. --------------------------------- Resolution: Done The prod upgrade has already happened. > Upgrade Narayana to 5.5.6.Final > ------------------------------- > > Key: WFLY-8485 > URL: https://issues.jboss.org/browse/WFLY-8485 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Beta1 > > > https://issues.jboss.org/projects/JBTM/versions/12334093 > https://github.com/jbosstm/narayana/compare/5.5.5.Final...5.5.6.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8671) Upgrade jboss-saaj-api_1.3_spec to 1.0.4.Final

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8671: ----------------------------------- Summary: Upgrade jboss-saaj-api_1.3_spec to 1.0.4.Final Key: WFLY-8671 URL: https://issues.jboss.org/browse/WFLY-8671 Project: WildFly Issue Type: Component Upgrade Components: EE Affects Versions: 11.0.0.Alpha1 Reporter: Ivo Studensky This upgrade involves JBEE-175 to fix Security Manager related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8670) Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8670: ----------------------------------- Summary: Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final Key: WFLY-8670 URL: https://issues.jboss.org/browse/WFLY-8670 Project: WildFly Issue Type: Component Upgrade Components: EE Affects Versions: 11.0.0.Alpha1 Reporter: Ivo Studensky The upgrade involves JBEE-176 to fix Security Manager related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8669) Upgrade jboss-saaj-api_1.3_spec to 1.0.4.Final

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8669: ----------------------------------- Summary: Upgrade jboss-saaj-api_1.3_spec to 1.0.4.Final Key: WFLY-8669 URL: https://issues.jboss.org/browse/WFLY-8669 Project: WildFly Issue Type: Component Upgrade Components: EE Affects Versions: 11.0.0.Alpha1 Reporter: Ivo Studensky This upgrade involves JBEE-175 to fix Security Manager related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8668) Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-8668?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-8668: -------------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final > ----------------------------------------------- > > Key: WFLY-8668 > URL: https://issues.jboss.org/browse/WFLY-8668 > Project: WildFly > Issue Type: Component Upgrade > Components: EE > Affects Versions: 11.0.0.Alpha1 > Reporter: Ivo Studensky > > The upgrade involves JBEE-176 to fix Security Manager related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8668) Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-8668: ----------------------------------- Summary: Upgrade jboss-jaxws-api_2.2_spec to 2.0.4.Final Key: WFLY-8668 URL: https://issues.jboss.org/browse/WFLY-8668 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 11.0.0.Alpha1 Reporter: Ivo Studensky The upgrade involves JBEE-176 to fix Security Manager related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8667) Elytron - unable to use OTP SASL mechanism

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8667: --------------------------------- Summary: Elytron - unable to use OTP SASL mechanism Key: WFLY-8667 URL: https://issues.jboss.org/browse/WFLY-8667 Project: WildFly Issue Type: Bug Components: Security Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Blocker I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1111) There is description of "case-sensitive" attribute inconsistency between model and XSD.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1111?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev reassigned ELY-1111: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > There is description of "case-sensitive" attribute inconsistency between model and XSD. > --------------------------------------------------------------------------------------- > > Key: ELY-1111 > URL: https://issues.jboss.org/browse/ELY-1111 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > > There is description of "case-sensitive" attribute inconsistency between model and XSD. > In XSD is missing default value. > Please add to XSD default value and unify description. > I suggest use description from model as right one: "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.". > *MODEL* > {code} > "case-sensitive" => { > "type" => BOOLEAN, > "description" => "Case sensitivity of the credential store. If case insensitive only lower case names are allowed for aliases.", > "attribute-group" => "implementation", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > *DMR* > {code} > <xs:attribute name="case-sensitive" type="xs:boolean" use="optional"> > <xs:annotation> > <xs:documentation> > Indicates that the credential store is case sensitive and should then allow for upper case in alias. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8661) Transaction is marked disassociated from application thread when transaction manager reaper thread suspends transaction

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8661?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-8661: ----------------------------------- Looks like we aren't notifying the association listeners in the case where the transaction is completed (either via commit or rollback). I'll file & link a JIRA. > Transaction is marked disassociated from application thread when transaction manager reaper thread suspends transaction > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8661 > URL: https://issues.jboss.org/browse/WFLY-8661 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Alpha1 > Reporter: Scott Marlow > Assignee: Scott Marlow > > I created a pull request to enable the TxTimeoutTestCase ([JBEAP-10550] + [WFLY-5319]) which required a test change, however, the test is failing for me locally, due to org.wildfly.transaction.client.LocalTransaction.suspend() calling notifyAssociationListeners(false) in the TM reaper "tx timeout" thread, which is wrong, as the app client thread may still be associated with the same transaction. > [https://gist.github.com/scottmarlow/1ae4a4abe98851b3fe6b1e602ba273d7] shows another reaper thread association call being made, that shouldn't be. > I'm not sure of how the Narayana org.jboss.tm.listener.TransactionListenerRegistry SPI, internally ensured that the reaper thread didn't incorrectly perform association/disassociation but what we have now in WildFly (appears) to be different. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2737) Elytron *-key-store should offer operations instead of alias resource

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2737?page=com.atlassian.jira.plugi... ] Ondrej Kotek moved JBEAP-10627 to WFCORE-2737: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2737 (was: JBEAP-10627) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta16 (was: 7.1.0.DR17) > Elytron *-key-store should offer operations instead of alias resource > --------------------------------------------------------------------- > > Key: WFCORE-2737 > URL: https://issues.jboss.org/browse/WFCORE-2737 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta16 > Reporter: Ondrej Kotek > Priority: Blocker > Labels: eap7.1-rfe-blocker > > Elytron {{*-key-store}} resources should offer operations instead of {{alias}} resource, at least {{ldap-key-store}} should. The reason is the same like for {{identity}} resource of Elytron modifiable realms, see [WFCORE-2691|https://issues.jboss.org/browse/WFCORE-2691?focusedCommentId=...] or related mailing thread on [wildfly-dev|http://lists.jboss.org/pipermail/wildfly-dev/2017-April/00589...]. > Setting priority to blocker, like for JBEAP-9547. The issue also brings some changes to EAP7-203 related tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017