[MODEXPW-260] Generated file can not be downloaded from the Export manager.ERROR: The provided token has expired. Created: 19/Sep/22  Updated: 04/Jan/24  Resolved: 07/Oct/22

Status: Closed
Project: mod-data-export-worker
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Olga Kondratenko Assignee: Oleksandr Bozhko
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified
Environment:

https://ptf-rmb.int.aws.folio.org/(lcp2)


Attachments: PNG File chrome_1HF0AcASHl.png     PNG File chrome_et8n4ptlZH.png    
Issue links:
Relates
relates to MODEXPW-204 User can see preview of the file of a... Closed
relates to MODEXPW-454 "Request has expired" or "Expired to... Open
relates to MODEXPW-234 Spike [Bulk-Edit]: temporary files o... Closed
Sprint: Firebird - Sprint 150
Story Points: 1
Development Team: Firebird
RCA Group: TBD

 Description   

Overview: After some time elapses, the files generated by Export manager cannot be downloaded from the Export manager and returning error: ERROR: The provided token has expired.

In scope of this task please document:

  • type of the token
  • how the token is configured

Additional information:

  1. Log into bugfest FOLIO environment as a User
  2. Go to the Export manager
  3. Click on the Job ID link of the job that was executed several days ago


<Error>
<Code>ExpiredToken</Code>
<Message>The provided token has expired.</Message>
<Token-0>IQoJ......</Token-0>
<RequestId>SQWE67TCEEDTDNQQ</RequestId>
<HostId>bRuAEHX+H1TTL3FUG11Re8XZu+CIyMtD8R7jJEeOnpuEr+Px1ulIpM41K85NvqAP1VYQDc6lLSc=</HostId>
</Error>

URL: https://data-export-folio-eis-us-east-1-int-tenant.s3.us-east-1.amazonaws.com/2022-09-16-Matched-Records-100-item-accession_num1.csv?X-Amz-Security-Token=IQoJb3JpZ2luX2VjEFgaCXVzLWVhc3QtMSJIMEYCIQCPawGEVozPK2JPn6hgZXT91Qi%2Fh1BghFJoP2yXHp3eqQIhAND6ONrABpWTBQvA6AONZHGudmFe94IPKpZocJCACdDvKvADCPD%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEQAxoMMDU0MjY3NzQwNDQ5IgwzK783u5%2Bl2qxgxHMqxAOHVM0TmZ23SKue2Czf3Bp%2BX9ialFbYm3c1URePEXNiifOkye5tO%2B7Dlnt1FQb1b%2FIt3MYFhEi5cGoiO4Pap6OPl1FSxwPZ%2BXyfb2NYenoCDWBONjcn7W4clpygS0%2F7nfF6umL67Dkz0FoOBlFkXtgbv8tEK7AEGj8s1otXDtpcr5FSlGBuEh1KyxC0cjG2VNSXNheoHeeDMbmR1P6VKoiiV1WF0z1LkAKVHuSwJZk4%2BMXIsr5ped9oTt%2FCJJsAm%2BOMnBAK0Fma045WKLYpozJ2bs0MTPJci7kF9NMjlIPJomLf%2BSkulJVdJHWo2uXL23PaZJxKLt0VI%2BFu4oJvCvcfQJMpJQUd7Tq6FyTl%2B3IpzOWIqnO%2BZieeWVct0e2KkqfcvUs%2FOY5%2BMFTwE4%2FqmZq9xTiT7UxLHSAWKaXI7821wYvgl2zgyGXgUAzmxD0%2Bv6NPr09isDyg%2BlLgBS3Uw4hggaMTBf64Ot05DbBK5Nw7kG0bjx8el0Mx2EqQlzalMaobhI7XNS%2Bg5fOfgxmAVIgbCQdwtevmcq8%2FFVcvaq2wkvqN%2FNooWBstrpx9Ho6UcgOnKfNeAri95W87fX%2BMiLgg63aarDDeo5KZBjqkAVFHkoPuhGs6kGJNcpUq7T2TAqBHkh3JQGjjUQYjunsrNxgNe3EcfWr4wKmxL4jXod6q4w5g3hLI0bvduizpXIqV2xUv%2BFdSCwdIzjsbOi9tKYZWOqmf8%2BbGjRNKtwyPIUl7o0I28xyT2vWtEU3xXlcvz%2F%2FSyZb%2BFV97Sz2GmAZJDB1KIuWfsoQmu6C9PdRBxvLuYHVAZH9Z4HrW9OI2sNaoGuHx&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAQZIU4AEQUZEYDV7Z%2F20220916%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220916T174547Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=5169af8a85c180880aa36f1b10c7dac4ab85ab27d2a64a09b90ff3643dde074f



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 19/Sep/22 ]

Hi Magda Zacharska There's no dev team on this bug - should it be Firebird? Thank you!

Comment by Olga Kondratenko [ 07/Oct/22 ]

Need to add some description to reproduce the issue:

Everything should be performed on the same calendar day UTC:
Upload file -> download Matched records (successful)

-> make changes -> download file with changes (successful)

-> wait for about 2 hours

-> upload a file with the same name -> download Matched records (The provided token has expired)

-> make changes -> download the file with changes (The provided token has expired)

Comment by Oleksandr Bozhko [ 07/Oct/22 ]

Hi Magda Zacharska. Assuming the stated above by Olga Kondratenko, the actual reason of this behavior is the logic of storing the files with the same names. We already have the spike MODEXPW-234 related to this problem and it is highly likely that this issue will disappear after the problems described in the spike are resolved.

Comment by Magda Zacharska [ 07/Oct/22 ]

To be addressed in MODEXPW-234 Closed

Generated at Thu Feb 08 22:30:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.