[MNT-18719] REST Task does not read endpoint configuration dynamically when deployed from one environment to another Created: 13-Oct-17  Updated: 02-Dec-19

Status: Open
Project: Service Packs and Hot Fixes
Component/s: APS Identify Manager, APS Kickstart/Studio
Affects Version/s: Alfresco Process Services 1.7
Fix Version/s: Alfresco Process Services .N

Type: Service Pack Request
Reporter: Hee Sun Park [X] (Inactive) Assignee: Mark Howarth [X] (Inactive)
Resolution: Unresolved Votes: 0
Labels: Modeler-Process, Rome
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive RestTest.zip     PNG File call_fails.PNG     PNG File process_stalls.PNG    
Issue Links:
Bug Priority:
Category 3
ACT Numbers:



not sure if this is bug or enhancement request

tested on 1.7.0 and 1.6.4.

Issue description
Currently, when deploying REST task, when the endpoint is configured in the IDM -> Endpoint -> with Basic Authentication, upon moving the app from one environment to another, it does not recognize the target environment's REST endpoint credentials dynamically.

Customers usually follow the development lifecycle and develop the app in the lower environments (DEV, TEST) using the lower environments endpoint credentials, but when the app development is complete and it is deployed to the higher environments (UAT or PROD), even though the endpoint configuration is identical, the credentials can be different.

What customer would like is that if there is an endpoint configured identically between higher and lower env, upon migrating the app, the app should dynamically detect the endpoint configured in the target environment and override the credentials of the source env basic auth packaged in the app depending on the name of the environment or the major path.

Steps to reproduce the issue

  1. set up 1.7.0 and deploy the attached app (RestTest.zip)
  2. The app is configured to use for the endpoint in the IDM -> Endpoint
  3. Basic authentication is enabled to use OOTB un:admin@app.activiti.com and pw:admin
  4. Please configure the endpoint to reflect the one in your test environment in IDM
  5. Once the endpoint is configured, the process will have to be modified to point to the correct endpoint in the target environment, then the app will work
  6. Once you confirm that the app works, export the app as a zip
  7. Deploy the app in a different environment where <server>:<host>/activiti-app/api-enterprise/ endpoint is configured
  8. Even though the path is identical, since the server name is different and possibly the credentials are different, the app does not work, unless the endpoint is modified accordingly in the process and the app is redeployed. (Please find the attached screenshots)

Desired Behavior

  1. The app detects identical path <server>:<host>/activiti-app/api-enterprise/ configured in the target environment and dynamically overrides the endpoint and publishes without the user/admin having to manually configure the endpoint upon importing the app and redeploying it in the target environment.

Use Case
Some customer environments do not allow manual configuration changes when apps are deployed from DEV to PROD. In that case, the app will not work.

Supporting Screenshots of the current behavior

  1. call_fails.png
  2. process_stalls.png
  3. RestTest.zip

Comment by Mark Howarth [X] (Inactive) [ 23-Aug-19 ]

Reassigning to Doug Gruber, the new PM for APS.

Comment by Mark Howarth [X] (Inactive) [ 02-Dec-19 ]

Assigning to Mark Howarth [X] as PM for APS.

Generated at Thu Jun 24 00:26:04 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.