Contrib.social

Disconnecting Acquia DAM and then changing the DAM domain allows users to still browse Old DAM assets.

Open on Drupal.org →
Created on 6 May 2024, over 1 year ago

Problem/Motivation

Currently once Acquia DAM has been connected and users have been authenticated, their tokens are saved in users_data table. If a site admin clicks on Disconnect DAM and afterwards changes the DAM domain to a different one, the user data for acquia_dam is not cleared and users are still able to connect to old DAM domain.

Steps to reproduce

  • Once DAM is connected and users have been using DAM in content creation, admin clicks on Disconnect Site button.
  • After disconnecting the site from DAM, change the DAM domain to a different valid URL.
  • Expected result: Users already authenticated to use DAM assets should be prompted to authenticate to new DAM.
  • Actual result: Users previously authenticated to use old DAM are still able to use Old DAM and are not prompted to re-authenticate to new DAM. Also any new users authenticating will be using new DAM.

Proposed resolution

Clear the users data on disconnecting DAM.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇮🇳India amangrover90

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @amangrover90
  • Comment over 1 year ago →
    🇮🇳India amangrover90
  • Merge request !49#3445449 – Clear users data on clicking Disconnect site button → (Open) created by amangrover90
  • Comment over 1 year ago →
    🇮🇳India amangrover90
  • Assigned to amangrover90
  • Status changed to Needs work over 1 year ago
  • Comment over 1 year ago →
    🇮🇳India amangrover90
  • Issue was unassigned.
  • Comment over 1 year ago →
    🇮🇳India amangrover90
  • Pipeline finished with Failed
    over 1 year ago
    Total: 2496s
    #165524
  • Pipeline finished with Failed
    over 1 year ago
    Total: 2488s
    #165528
  • Pipeline finished with Failed
    over 1 year ago
    Total: 2553s
    #165529
  • Comment over 1 year ago →
    🇭🇺Hungary Balu Ertl Budapest 🇪🇺

    Tested, found working as expected. The bugfix itself is RTBC'd but we still need add test coverage.

    Set target branch to the latest dev version. Also, renamed ticket to describe the desired situation.

  • Pipeline finished with Failed
    over 1 year ago
    Total: 3163s
    #169456
  • Pipeline finished with Failed
    over 1 year ago
    Total: 2981s
    #180412
  • Comment 12 months ago →
    🇭🇺Hungary Balu Ertl Budapest 🇪🇺

    As being a bugfix, it supposed to target the 1.0.x branch. Sorry for confusion earlier.

  • First commit to issue fork.
  • Pipeline finished with Success
    7 months ago
    Total: 2212s
    #452259
  • Pipeline finished with Success
    5 months ago
    #489051
  • Pipeline finished with Failed
    5 months ago
    Total: 2364s
    #490187
  • Pipeline finished with Failed
    4 months ago
    Total: 2459s
    #507146
  • Pipeline finished with Success
    about 2 months ago
    Total: 2003s
    #573052
  • Pipeline finished with Failed
    6 days ago
    Total: 1897s
    #611420
  • Pipeline finished with Failed
    4 days ago
    Total: 1909s
    #613532
  • Pipeline finished with Failed
    3 days ago
    Total: 2074s
    #614687
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024