Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using one Craft CMS instance as an identity provider for another? #105

Open
ericdrosas87 opened this issue Sep 19, 2022 · 1 comment
Open
Assignees
Labels
question Further information is requested

Comments

@ericdrosas87
Copy link

I'm part of the LSST/Rubin Observatory team that has already implemented this plugin into our main PR website, and I have been tasked with looking into if we can use that main PR website as an identity provider for another site.

Use case:
We have a separate Craft CMS (let's call it the Education CMS) we are standing up and we would like to authenticate into this new Craft instance via the main PR website's JWT graphQL endpoint.

Questions:

  • Is this possible with the plugin off-the-shelf? If not, how much custom development would be needed to make this work?
  • We would like to maintain a separate, dedicated database for the Education CMS, if the answer to the above question is yes, will it make "duplicate" entries, one DB record in each CMS database?

Please let me know if you need more information in order to answer the above questions.

@jamesedmonston jamesedmonston self-assigned this Sep 20, 2022
@ericdrosas87
Copy link
Author

Any updates on this?

@jamesedmonston jamesedmonston added the question Further information is requested label Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants