[EXTDAM-71] Bynder & S3. Fix caching when changing credentials/ token in Password app Created: 20/Feb/20  Updated: 10/Mar/20  Resolved: 10/Mar/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Yen Lac Tue Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.5h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon EXTDAM-80 Sort out Bynder token problems Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: DAMs backend
Sprint: Add-Ons 32, Add-Ons 33
Story Points: 2

 Description   

Description:
After accessing S3 and Bynder, the user goes to Passwords app to update AWS credentials/Bynder token.

S3/Bynder don't load items according to new credentials/token.

 

AC:

  • S3/Bynder should reload items once AWS credentials/token have been updated in Passwords app.


 Comments   
Comment by Jesus Alonso [ 04/Mar/20 ]

I'm sorry, I confused it with ADCOM-2 (also related to cache updates)

Generated at Mon Feb 12 01:51:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.