search

adobe / helix-sidekick-extension

Browser extension for authors on AEM projects
Apache License 2.0
21 stars 36 forks source link

Multiple logins required different projects but a single organization #712

Closed mokimo closed 4 months ago

mokimo commented 4 months ago

Problem statement

For Adobe.com we have a bunch of different projects (cc, dc, bacom, etc.) and authors commonly need to work across different projects. Currently authors are logging in on a chain of projects, let's say four different ones to make some metadata changes.

Expected Behaviour

When working on an organization that has multiple projects, a sidekick login should only be required once.

Actual Behaviour

Each project needs a separate login, despite being entitled to view/preview/edit/publish/etc. multiple projects within an organization.

Reproduce Scenario (including but not limited to)

Requirement: being part of the adobecom MS Org

  1. Log into https://main--cc--adobecom.hlx.page/drafts/osahin/test-gnav (MS Auth, then Sidekick)
  2. Log into https://main--bacom--adobecom.hlx.page/ (MS Auth, then Sidekick)
  3. Log into https://main--dc--adobecom.hlx.page/acrobat/ (MS Auth, then Sidekick)

6 Log ins, for three projects.

Steps to Reproduce

☝️

Platform and Version

Sidekick version 6.42.0

mokimo commented 4 months ago

@rofe would be lovely if this authoring and developer experience could be improved for customers that have multiple projects with a single user/email being entitled to make changes across different projects. We heard numerous complaints from our authors and would love to hear if the product team sees value in improving this.

trieloff commented 4 months ago

:tada: This issue has been resolved in version 6.43.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: