September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13879) Upgrade Mojarra to 2.3.14.SP01

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13879?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13879: ------------------------------ Description: We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest upstream bug fixes. We should also backport the upstream fix for WFLY-12677 since it hasn't been included in a 2.3.x release yet. (was: We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest upstream bug fixes. We should also backport the upstream fix for WFLY-12677.) > Upgrade Mojarra to 2.3.14.SP01 > ------------------------------ > > Key: WFLY-13879 > URL: https://issues.redhat.com/browse/WFLY-13879 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest upstream bug fixes. We should also backport the upstream fix for WFLY-12677 since it hasn't been included in a 2.3.x release yet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13879) Upgrade Mojarra to 2.3.14.SP01

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13879?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13879: ------------------------------ Description: We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest bug fixes. We should also backport the upstream fix for WFLY-12677. > Upgrade Mojarra to 2.3.14.SP01 > ------------------------------ > > Key: WFLY-13879 > URL: https://issues.redhat.com/browse/WFLY-13879 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest bug fixes. We should also backport the upstream fix for WFLY-12677. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13879) Upgrade Mojarra to 2.3.14.SP01

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13879?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13879: ------------------------------ Summary: Upgrade Mojarra to 2.3.14.SP01 (was: Upgrade Mojarra to 2.3.9.SP13) > Upgrade Mojarra to 2.3.14.SP01 > ------------------------------ > > Key: WFLY-13879 > URL: https://issues.redhat.com/browse/WFLY-13879 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13873) Upgrade RESTEasy to 3.13.2.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13873?page=com.atlassian.jira.plugi... ] Ronald Sigal closed WFLY-13873. ------------------------------- Resolution: Won't Do > Upgrade RESTEasy to 3.13.2.Final > -------------------------------- > > Key: WFLY-13873 > URL: https://issues.redhat.com/browse/WFLY-13873 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Upgrade from 3.11.2.Final to 3.12.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ] Richard Achmatowicz edited comment on WFLY-13871 at 9/16/20 4:09 PM: --------------------------------------------------------------------- I've implemented the PR using the shortcut approach described above. [~jbaesner] if you can give this a try, i'd appreciate it. was (Author: rachmato): I've implemented the PR using the shortcut approach described above. > Re-implement correct suspend/resume behaviour for EJB client > ------------------------------------------------------------ > > Key: WFLY-13871 > URL: https://issues.redhat.com/browse/WFLY-13871 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 21.0.0.Beta1 > > > When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations. > This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored. > This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13871: -------------------------------------------- I've implemented the PR using the shortcut approach described above. > Re-implement correct suspend/resume behaviour for EJB client > ------------------------------------------------------------ > > Key: WFLY-13871 > URL: https://issues.redhat.com/browse/WFLY-13871 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 21.0.0.Beta1 > > > When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations. > This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored. > This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ] Sonia Zaldana reassigned WFLY-11492: ------------------------------------ Assignee: Sonia Zaldana > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.redhat.com/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation, Security > Reporter: Alan Hantke > Assignee: Sonia Zaldana > Priority: Major > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13879) Upgrade Mojarra to 2.3.9.SP13

by Farah Juma (Jira)

Farah Juma created WFLY-13879: --------------------------------- Summary: Upgrade Mojarra to 2.3.9.SP13 Key: WFLY-13879 URL: https://issues.redhat.com/browse/WFLY-13879 Project: WildFly Issue Type: Component Upgrade Components: JSF Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2541) CS, MASK-password must support same MASKED string without SALT and ITERATION as old vaults system.

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFCORE-2541?page=com.atlassian.jira.plug... ] Sonia Zaldana resolved WFCORE-2541. ----------------------------------- Resolution: Rejected > CS, MASK-password must support same MASKED string without SALT and ITERATION as old vaults system. > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-2541 > URL: https://issues.redhat.com/browse/WFCORE-2541 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Priority: Major > > MASK-password must support same MASKED string without SALT and ITERATION as old vaults system. > MASKED password in Elytron has this format > {code} > MASK-KAwLfD1BN8WFhZptWsa17G==;12345678;230 > {code} > But old vault system has SALT and ITERATION as global parameters for all MASK-strings same. > And you have this format of MASKED password > {code} > MASK-KAwLfD1BN8WFhZptWsa17G== > {code} > It would be better add there original approach too because of migration... > Please add there this default option: > * set SALT and ITERATION default values for using of credential stores. If will be defined MASK-string without SALT and ITERATION then will be used these values. > * if you use MASK-string;SALT;ITERATION form, then will be used SALT and ITERATION from this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-932) Wrong log exception in jdbc-realm

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-932?page=com.atlassian.jira.plugin.s... ] Sonia Zaldana resolved ELY-932. ------------------------------- Resolution: Out of Date > Wrong log exception in jdbc-realm > --------------------------------- > > Key: ELY-932 > URL: https://issues.redhat.com/browse/ELY-932 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Kotek > Assignee: Pedro Igor Silva > Priority: Minor > > There is {{ldap-realm}} log exception in {{jdbc-realm}}, see https://github.com/wildfly-security/wildfly-elytron/blob/ce3475fbc7456936... > A new log message will be necessary. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 September 2020