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

  1. Once DAM is connected and users have been using DAM in content creation, admin clicks on Disconnect Site button.
  2. After disconnecting the site from DAM, change the DAM domain to a different valid URL and submit the form.
  3. Expected result: Users already authenticated to use DAM assets should be prompted to authenticate to new DAM.
  4. 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

Tests

User interface changes

API changes

Data model changes

Issue fork acquia_dam-3445449

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

amangrover90 created an issue. See original summary.

amangrover90’s picture

amangrover90 commented
Issue summary: View changes

amangrover90 opened merge request !49

amangrover90’s picture

amangrover90 commented
Issue summary: View changes
amangrover90’s picture

amangrover90 commented
Assigned: Unassigned » amangrover90
Status: Active » Needs work
amangrover90’s picture

amangrover90 commented
Assigned: amangrover90 » Unassigned
baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented
Title: Disconnecting Acquia DAM and then changing the DAM domain allows users to still browse Old DAM assets. » Ensure user authentication data being flushed when swapping DAM domains
Version: 1.0.12 » 1.1.x-dev
Issue summary: View changes

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.

baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented
Version: 1.1.x-dev » 1.0.x-dev

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

rajeshreeputra made their first commit to this issue’s fork.

rajeshreeputra’s picture

rajeshreeputra
he/him
Location Pune
commented
Version: 1.0.x-dev » 1.1.x-dev
Status: Needs work » Needs review

Requesting review.

rajeshreeputra’s picture

rajeshreeputra
he/him
Location Pune
commented
Status: Needs review » Fixed

MR merged!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.