April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1955) (7.3.z) Submission for "j_security_check" login does not work if URL has no trailing slash

by Ilia Vassilev (Jira)

Ilia Vassilev created ELY-1955: ---------------------------------- Summary: (7.3.z) Submission for "j_security_check" login does not work if URL has no trailing slash Key: ELY-1955 URL: https://issues.redhat.com/browse/ELY-1955 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Ilia Vassilev Assignee: Darran Lofthouse Attached file "Security.ear" contains a web application with a single jsp page "index.jsp" and form based login, which is secured by a Database Identity Store (Elytron). When calling the root URL of the webapp without specifiying any page and {color:red}*no*{color} trailing slash (http://localhost:8080/SecurityWeb), on WildFly 11 the login form is shown, and then the welcome file "index.jsp" is shown. On WildFly 19, the login form is shown, and after successful login, there is an error message "404 - Not Found", and the URL in the adress bar changes to http://localhost:8080/j_security_check It works if the URL is "http://localhost:8080/SecurityWeb/" (trailing slash). It seems WildFly 11 appends the "/" automatically when redirecting to the login form, while WildFly 19 keeps this URL. To run the sample, you have to add the Elytron config - the script "configure.cli" can be used for this: jboss-cli.bat --file=path_to\configure.cli The script "restore-configuration.cli" undoes this configuration. Username/Password are e.g. "admin"/"admin" - the sample creates a user table based on an ejb and "import.sql" inserts users. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4395) JDR collect free disk space

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-4395?page=com.atlassian.jira.plugin... ] Ranabir Chakraborty commented on WFLY-4395: ------------------------------------------- [~bmaxwell] Can you please provide some steps to recreate this issue? > JDR collect free disk space > --------------------------- > > Key: WFLY-4395 > URL: https://issues.redhat.com/browse/WFLY-4395 > Project: WildFly > Issue Type: Enhancement > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Major > > JDR collect free disk space as server can throw errors when there is no free space. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5270) Refactor KiePMMLPredicate AST Factories

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5270: ---------------------------------------- Summary: Refactor KiePMMLPredicate AST Factories Key: DROOLS-5270 URL: https://issues.redhat.com/browse/DROOLS-5270 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Refactor AST factories to avoid duplicated code for tree and scorecard models -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13394) Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13394?page=com.atlassian.jira.plugi... ] Jean Francois Denise updated WFLY-13394: ---------------------------------------- Summary: Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final (was: Release org.jboss.universe.producer:wildfly-producers:1.2.0.Final) > Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final > ----------------------------------------------------------------- > > Key: WFLY-13394 > URL: https://issues.redhat.com/browse/WFLY-13394 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 19.1.0.Final > > > Pick up https://github.com/wildfly/wildfly-producers/issues/11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13394) Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13394?page=com.atlassian.jira.plugi... ] Jean Francois Denise reassigned WFLY-13394: ------------------------------------------- Assignee: Jean Francois Denise (was: Brian Stansberry) > Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final > ----------------------------------------------------------------- > > Key: WFLY-13394 > URL: https://issues.redhat.com/browse/WFLY-13394 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Jean Francois Denise > Priority: Blocker > Fix For: 19.1.0.Final > > > Pick up https://github.com/wildfly/wildfly-producers/issues/11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13394) Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13394?page=com.atlassian.jira.plugi... ] Jean Francois Denise resolved WFLY-13394. ----------------------------------------- Resolution: Done > Release org.jboss.universe.producer:wildfly-producers:1.1.3.Final > ----------------------------------------------------------------- > > Key: WFLY-13394 > URL: https://issues.redhat.com/browse/WFLY-13394 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Jean Francois Denise > Priority: Blocker > Fix For: 19.1.0.Final > > > Pick up https://github.com/wildfly/wildfly-producers/issues/11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4945) (7.3.z) Reading of identity from security domain causes NPE

by Ilia Vassilev (Jira)

Ilia Vassilev created WFCORE-4945: ------------------------------------- Summary: (7.3.z) Reading of identity from security domain causes NPE Key: WFCORE-4945 URL: https://issues.redhat.com/browse/WFCORE-4945 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ilia Vassilev Assignee: Diana Vilkolakova Fix For: 12.0.0.Beta2 Security domain in the elytron subsystem has operation `read-identity`. Description of this opearation is the following: `Reads an identity from a security domain if it exists.` However, this operation causes NPE when called on the security domain backed by the filesystem realm (see steps to reproduce) or jdbc realm. This issue is to address that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4905) Provide common capability for Remoting connectors

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4905?page=com.atlassian.jira.plug... ] Darran Lofthouse reopened WFCORE-4905: -------------------------------------- Reopening, the PR for this change needs to be submitted against master not the 11.0.x branch. > Provide common capability for Remoting connectors > ------------------------------------------------- > > Key: WFCORE-4905 > URL: https://issues.redhat.com/browse/WFCORE-4905 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 11.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 12.0.0.Beta2 > > > The EJB3 subsystem has an element <remote/> which performs a few different functions relating to external clients accessing EJBs on the server: > * sets up a Remoting connector service so that external clients may connect to the server using EJB / Remoting or EJB / HTTP Upgrade / Remoting > * sets up client mappings entries for those remote clients which are used in topology updates to allow the client to find the server's connectors > The Remoting subsystem has two connector types which may be supplied to the <remote connector-ref/> attribute. <connector name="remoting-connector"/> represents a Remoting endpoint and <http-connector name="http-connector"/> represents an Undertow listener which may be used with HTTP Upgrade. > At present, in the Remoting subsystem, these connectors have two separately defined capabilities: > // for <connector/> > private static final String CONNECTOR_CAPABILITY_NAME ="org.wildfly.remoting.connector"; > static final RuntimeCapability<Void> CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(CONNECTOR_CAPABILITY_NAME, true).build(); > // for <http-connector/> > private static final String HTTP_CONNECTOR_CAPABILITY_NAME = "org.wildfly.remoting.http-connector"; > static final RuntimeCapability<Void> HTTP_CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(HTTP_CONNECTOR_CAPABILITY_NAME, true).build(); > The proposal here is to allow referencing both connectors using a single capability base name, "org.wildfly.remoting.connector" to simplify specification of the capabilities which the <remote/> element needs (i.e. it may depend on one or the other). These are both dynamically named capabilities, so their names will vary based on the name of the management resource instance they represent. Because capability names are considered public API, the existing capability name for org.wildfly.remoting.http-connector cannot be removed to further simplify. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13401) MicroProfile REST Client does not handle header propagation correctly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13401?page=com.atlassian.jira.plugi... ] James Perkins closed WFLY-13401. -------------------------------- Resolution: Duplicate Issue > MicroProfile REST Client does not handle header propagation correctly > --------------------------------------------------------------------- > > Key: WFLY-13401 > URL: https://issues.redhat.com/browse/WFLY-13401 > Project: WildFly > Issue Type: Bug > Components: MP REST Client > Reporter: James Perkins > Assignee: Alessio Soldano > Priority: Major > > The linked forum post has some good detail on what the issue is. The gist of it is the {{org.eclipse.microprofile.rest.client.propagateHeaders}} does not seem to propagate the properties to the request headers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13397) MP HeaderPropagation does not propagate headers

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13397?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFLY-13397: ------------------------------------ Assignee: (was: Brian Stansberry) > MP HeaderPropagation does not propagate headers > ----------------------------------------------- > > Key: WFLY-13397 > URL: https://issues.redhat.com/browse/WFLY-13397 > Project: WildFly > Issue Type: Bug > Components: MP REST Client > Affects Versions: 19.0.0.Final > Reporter: Thimo König > Priority: Major > Attachments: mp-headerpropagation-1.0.0-SNAPSHOT-sources.jar, mp-headerpropagation-1.0.0-SNAPSHOT.war, openliberty_response.json, wildfly_response.json > > > When calling a JAX-RS Resource from another JAX-RS Resource using the MP RestClient the propagation of headers does not work. I have created a sample app which is available on github https://github.com/koenigt/headerpropagation and attached [^mp-headerpropagation-1.0.0-SNAPSHOT.war] to this report aswell. > Deploy the sample app and use CURL like: > {code} > curl -i -H "Accept: application/json" -H "Header2Propagate: PropagatedValue" http://localhost:8080/mp-hp/api/client {code} > The expected result should be: > {code:JSON} > { > "Name": "ClientResource", > "org.eclipse.microprofile.rest.client.propagateHeaders": "Authorization,Accept-Language,Header2Propagate", > "IncomingRequestHeaders": { > "Accept": "[*/*]", > "accept-encoding": "[gzip, deflate, br]", > "Cache-Control": "[no-cache]", > "connection": "[keep-alive]", > "Content-Type": "[null]", > "Header2Propagate": "[PropagatedValue]", > "Host": "[localhost:9080]", > "Postman-Token": "[8105e2ef-9b5f-4b3f-a7a9-cea73d51efee]", > "User-Agent": "[PostmanRuntime/7.24.0]" > }, > "ServerResponse": { > "Name": "ServerResource", > "IncomingRequestHeaders": { > "Accept": "[application/json]", > "Cache-Control": "[no-cache]", > "connection": "[keep-alive]", > "content-type": "[application/json]", > "Header2Propagate": "[PropagatedValue]", > "Host": "[localhost:9080]", > "MyClientHeader": "[newHeaderValue]", > "Pragma": "[no-cache]", > "User-Agent": "[Apache-CXF/3.3.3-SNAPSHOT]" > } > } > } > {code} > but since the header is not propagated you are getting only this: > {code:JSON} > { > "Name": "ClientResource", > "org.eclipse.microprofile.rest.client.propagateHeaders": "Authorization,Accept-Language,Header2Propagate", > "IncomingRequestHeaders": { > "Accept": "[*/*]", > "Accept-Encoding": "[gzip, deflate, br]", > "Cache-Control": "[no-cache]", > "Connection": "[keep-alive]", > "Header2Propagate": "[PropagatedValue]", > "Host": "[localhost:8080]", > "Postman-Token": "[6e36736f-3b55-4f34-9f39-063dbd4f4e8f]", > "User-Agent": "[PostmanRuntime/7.24.0]" > }, > "ServerResponse": { > "Name": "ServerResource", > "IncomingRequestHeaders": { > "Accept": "[application/json]", > "Connection": "[Keep-Alive]", > "Host": "[localhost:8080]", > "User-Agent": "[Apache-HttpClient/4.5.11 (Java/12)]", > "uber-trace-id": "[a0d9d0ac4c54614%3Ac82190f35d41f958%3Aa0d9d0ac4c54614%3A1]" > } > } > } > {code} > This issue has already been discussed on https://groups.google.com/forum/#!topic/wildfly/QOx3AfrXAMc and Rebecca Searls (rseals(a)redhat.com) ask me to file this bug report -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 2020