Sidekick Authentication across sites

[sukamat]

Is your feature request related to a problem? Please describe.
We have multiple sites in the "adobecom" space. Eg: dc, bacom, homepage etc. Sidekick auth has been enabled for these sites. The ask is if the author authenticates on one, they get authenticated automatically on other sites as well.

There are 2 use-cases for this ask:

1. When an author authenticates on DC sidekick and then opens a document in homepage, they need to authenticate again. This will help an author working across sites to authenticate once and remain signed-in when they work on other site documents.
2. We have a tool in Milo that checks the page status across these different sites and requires the user to be signed-in across these sites for the tool to work.

Describe the solution you'd like
Add a feature in the sidekick to remain signed-in across sites (SSO)? Perhaps if the owner is the same for the sites? All these sites are under https://github.com/adobecom

Any other way to make this easier for the author as well as for the tool to work across sites without making the author sign-in into the sidekick separately?

[rofe]

@tripodsan FYI

[mokimo]

@rofe @tripodsan since we have a central content repository on adobe.com now, this issue becomes more obvious. Any guidance?

[dylandepass]

@rofe On the sidekick side, is the issue here not that the token is stored by owner/repo is session storage?

Maybe a way to link projects in the sidekick could fix this.. If projects are linked than a login to one of them would persist the auth token in all linked projects.

[mokimo]

For my understanding, are there two different tokens?

• One for the sidekick
• One for site auth

The bigger issue would be site auth rather than logging into a specific project to preview/publish. Although only one sign in for everything would be the perfect experience.

[rofe]

I think this is a duplicate of #559