[UXPROD-3449] Use specific user for scheduled SUSHI harvesting Created: 14/Dec/21  Updated: 14/Dec/21  Resolved: 14/Dec/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Annika Schröer Assignee: Annika Schröer
Resolution: Done Votes: 0
Labels: eUsage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODEUSHARV-50 Use system user for scheduled harvesting Closed
Requires
is required by MODEUSHARV-47 Endpoint w/o required permissions Closed
Release: Lotus R1 2022
Development Team: Leipzig
PO Rank: 0

 Description   

Current situation or problem:

Currently, the harvesting endpoint is not requiring any permissions to start the harvester, because only users, not modules, can be assigned with permissions. For scheduled periodic harvestings, there is no user involved. 

In scope

To be able to protect the endpoint by permissions, eUsage will now require to set up a specific user account (named e.g.  mod-erm-usage-harvester) that is assigned the necessary permissions and is registered to the harvester module in an environment variable. This user will then trigger the scheduled harvesting.

This feature includes:

  • adding permissions to the harvester endpoint
  • add the new permissions to the visible permission "eUsage harvester: All permissions for eUsage harvester module", to be assigned to "real" users that will start the harvester manually
  • registering the user account and password via environment variables
  • involving the user in the scheduled harvesting start process

 

 



 Comments   
Comment by Annika Schröer [ 14/Dec/21 ]

Documentation of the implemented solution: https://github.com/folio-org/mod-erm-usage-harvester#periodic-harvesting

Generated at Fri Feb 09 00:32:05 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.