Hi All. First I’ll like thank the Ory team for bui...
# talk-kratos
b
Hi All. First I’ll like thank the Ory team for building such a great solution for Identity and Access. After using Keycloak, seemed like breeze 😜 . We are currently towards the end of the evaluation and would loke to adopt the stack for our product. I have a question though regarding the setup. We have 3 different types of identities and each of thise identity needs a self service. With the OSS you can only use the default schema as self service (please correct me if I made a mistake). So the solution we thought is to run 3 Kratos instance pointing to same db but having different identity config. Is that a correct design decision from your perspective. Sure we are looking at Ory Network and utilise the Organisations in future.
s
I don't work for Ory but this is the way I have been told to handle this scenario, depending on support within one configuration.
b
Thanks @shy-vr-32229 . And how are you resolving which instance to forward the request to.. we used the return_to query param to determine the instance .. any other interesting way ?
s
@bulky-lock-43792 we didn't end up going this route because our use cases changed, but, we did end up building a facade service in front of Kratos as we are integrating multiple IDPs and handling sessions across all of those.
If we add future Kratos use cases in the future we'll likely handle it in our facade/aggregation layer which fronts Kratos
b
Doing the same here as well
Thanks for the info 🙏