[AGS] AGS hardcodes /share context in multiple locations

Description

Problem Description

Customer has changed the /share context to another context (presumably by renaming the war, and setting share.context property). Share is functioning properly. However, they have noticed some AGS functionality doesn't work.

Steps to Reproduce
1. Install AGS 3.3.1
2. Rename share.war to foo.war
3. Set share.context=foo
4. Go to Admin Tools > Security Controls > Configure
5. Click "Classification Reasons" tab

Expected Behavior
Classification Reasons page is rendered.

Observed Behavior
An error is thrown: "We couldn't load the data. Try refreshing your screen, or check with your Alfresco Administrator that the server is running."

Notes

We hardcode the /share context in several places. We should instead use the value of share.context. See:

https://github.com/Alfresco/governance-services/search?q=%22%2Fshare%2Fproxy%22

Environment

None

Testcase ID

None

Activity

Show:
Rodica Sutu
April 2, 2021, 7:25 AM
Edited

Tested the issue by renaming the war file and changing the share.context property and the issue doesn’t reproduce on AGS 3.5.1-SNAPSHOT. Before closing this we need to set the correct Fix Version

Cezar Leahu
March 30, 2021, 1:28 PM

We have a fix for this issue in review for the master branch.

While this seem to be an older issue (affected versions include 3.3.0.4, 3.3.1, 3.4.1.1), there's no Fix version set on the JIRA ticket. We would like to know how far back we should backport the fix.

Fixed

Assignee

Rodica Sutu

Reporter

Scott Ashcraft

Labels

Escalated By

None

Security Issue

None

ACT Numbers

01021202

Premier Customer

None

Code Branch

None

Build Location

None

Regression Since

None

Work Funnel End

None

Patch Attached

None

Dependent Version/s

None

Cloud or Enterprise

None

Prioritization Score

None

Delivery Team

Team Apps2

Bug Priority

Category 2

Components

Fix versions

Affects versions