11

For Sitecore 9.1, can the Identity Server be used for multiple sites/clients? For example, on a local developer machine I have several 9.1 installs for separate clients. Could I use that Identity Server for the login for all of them? Or do i need a a separate Identity Server install for each client?

The problem I see is that the Identity Server needs to use a Core database, but if I use the Core DB for Client A, then Clients B and C would also have their info stored in the Client A Core DB.

Another problem I see is the Password Recovery Url used by the Identity Server. If I set the url to be for client A (https://clientA) and client B (https://clientB) needs a password reset, does client B get redirected to the https://clientA url?

Improve this question
5
  • I have an open ticket right with support. I think Sitecore has twisted IS4 for their own use and it’s not very useful as a real identity server, for other sites. I can get the site to generate bearer tokens and OAuth but they can’t be used as security. And there is no consent page. I guess we will see what comes out of it.
    – Chris Auer
    Jan 17, 2019 at 20:24
  • I'd explore adding a custom module as per doc.sitecore.com/developers/91/sitecore-experience-management/… and doc.sitecore.com/developers/91/sitecore-experience-management/…
    – Mark Gibbons
    Jan 20, 2019 at 4:19
  • @MarkGibbons I appreciate your comment, but could you elaborate more on how this would address or solve my question(s)? I'm not really looking for it to be a gateway to other providers, but to simply handle the logging in/out of multiple clients.
    – Ted Osberg
    Jan 21, 2019 at 18:07
  • I think that you'd have to add a custom subprovider for each site or client you want the identity server to handle.
    – Mark Gibbons
    Jan 22, 2019 at 0:09
  • 1
    I think we can do as 1. moving Sitecore Security membership provider from the Core database to individual database. i.imgur.com/bwnx3OC.png 2. Sitecore Identity Server - change connection string to newly created database. i.imgur.com/hII0cfq.png 3. Sitecore (ClientA/ClientB) - Finalize one sitecore instance where users can create or use for password recovery. Change "security" connection string to newly created database. i.imgur.com/rHQ0kmN.png.
    – venkat
    Jun 5, 2019 at 2:32

1 Answer 1

Reset to default
-1

you can do extract the Authentication related tables outside the core db and use the same for all users to identity-server. You need to do some customization to sync the user from that common db to Sitecore Core Db.

Improve this answer
1
  • This should ideally work
    – Vikash Raaj
    Feb 16, 2021 at 8:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.