While Saving a flow user receives forbidden hub error

Products

• CA Agile Requirements Designer

Issue/Introduction

While Saving a flow to hub user receives forbidden hub error
This is happening to a specific set of users, but not all.

Environment

Release : 3.0

Component : CA Agile Requirements Designer

Resolution

From the screenshot and logs, this looks like the user is seeing the error when attempting to load a flow, or subflow, or version there of, and not while saving it. The error points to improper read rights to the specific project/flow/version.

In the example snippet from the logs - notice how the user tries to GET a flow (probably to refresh subflows), but fails (because of the lack of proper permissions):

2020-05-04 22:03:25,993 INFO [default] [Agile Requirements Designer Hub Log](GET) Request URL: http://host.corp.domain.com:8081/ard/api/flow-storage/v1/versions/815c6a6d-9733-43ac-9490-0997a5101004/referenced-versions
2020-05-04 22:03:26,431 ERROR [default] [e:\buildagent\tdm\agiledesigner\agiledesigner\restservicehelper.cpp:579] [Agile Requirements Designer Hub Log]Qt Network Error (Qt error code: 201) Error transferring http://host.corp.domain.com:8081/ard/api/flow-storage/v1/versions/815c6a6d-9733-43ac-9490-0997a5101004/referenced-versions - server replied:
2020-05-04 22:03:26,434 INFO [default] [Agile Requirements Designer Hub Log]Response URL: http://host.corp.domain.com:8081/ard/api/flow-storage/v1/versions/815c6a6d-9733-43ac-9490-0997a5101004/referenced-versions
2020-05-04 22:03:26,434 INFO [default] [Agile Requirements Designer Hub Log]Response HTTP Code: 403
2020-05-04 22:03:26,434 INFO [default] [Agile Requirements Designer Hub Log]ReturnedMessage: {"timestamp":"2020-05-04T16:33:26.432+0000","status":403,"error":"Forbidden","message":"Forbidden","path":"/ard/flow-storage/v1/versions/815c6a6d-9733-43ac-9490-0997a5101004/referenced-versions"}

The Qt error code:201 = ContentAccessDenied - the access to the remote content was denied (similar to HTTP error 403), and results in the HTTP 403 Forbidden error.

From what we can tell, the user simply doesn't have the required access (read access) to the specific flow/subflow version. Make sure all users have access to all the resources they require (e.g. at least read access to subflows they use in their main flows).