0046580: junit DataSourceSecurity.fetchShouldBeAllowedOnlyIfRoleIsGranted fails on Tomcat9 (only for Datasource: AccountTreeMovement)

Description

This junit test fails when application is deployed on tomcat 9.x but only for the specific datasource AccountTreeMovement.
It shows 4 failures as four RoleTypes are tested for each dataSource.

Problem is the test triggering the following error on tomcat 9.x:
May 05 12:27:36 ip-172-31-9-130 tomcat9[2709]: Error parsing HTTP request header
May 05 12:27:36 ip-172-31-9-130 tomcat9[2709]: Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
May 05 12:27:36 ip-172-31-9-130 tomcat9[2709]: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Steps To Reproduce

Deploy application with tomcat 9.x
ant run.test -Dtest=org.openbravo.test.datasource.DataSourceSecurity

Check result*.xml file in src/ folder for the result of the test run

Proposed Solution

Fix the invalid request target (values in url) to be valid.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

blocks

backport

0046579

PR21Q2

closed

alostale

junit DataSourceSecurity.fetchShouldBeAllowedOnlyIfRoleIsGranted fails on Tomcat9 (only for Datasource: AccountTreeMovement)

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2021-05-07 11:31	alostale	Target Version	=> PR21Q2
2021-06-16 13:39	alostale	Status	scheduled => resolved
2021-06-16 13:39	alostale	Fixed in Version	=> PR21Q2
2021-06-16 13:39	alostale	Fixed in SCM revision	=> 7383d37dc6b338cc677c5a59fd790363bab2d442
2021-06-16 13:39	alostale	Resolution	open => fixed
2021-06-16 13:39	alostale	Status	resolved => closed
2021-06-16 13:39	alostale	Fixed in SCM revision	7383d37dc6b338cc677c5a59fd790363bab2d442 => https://gitlab.com/openbravo/product/openbravo/-/commit/7383d37dc6b338cc677c5a59fd790363bab2d442 [^]