First of all thank you for your detailed answer that gives me a lot of options to explore.
Sorry for the long post I hope I managed to give a clearer idea of what I’m trying to achieve below.
I should have explained here that my goal is to have on my production stack edx site several instances on the same server in order to have something like one course catalog for internal usage and one for external partners and customers.
I would like to have two sites on the same server and only allow users to connect to one site and not the other.
At the moment I’m exploring ways to achieve that on devstack before doing the same architecture on production stack.
Regarding my issue with the saml third authentication login so I have two different SAML applications on Okta to serve as identity provider. And I’m trying to integrate those two providers on edX.
About the saml configuration I have right now see below :
on the first site hosted in domain.example.com I created a SAML configuration with the unique slug = internal I created my set of keys and left the advanced config by default
And I have basically the same config for my second site hosted on otherdomain.example.com with another set of keys and the slug = external
Then I create two saml identity providers configuration one for each site to use those samlconfiguration one with the slug internal the other external. They are basically identical except for the entity and metadata source fields that each points to the correct Okta third party identity provider.
My issue is that I can only see on one site’s login page the third auth button to redirect the user to the third party authentication page. For the other one the button is not visible and when I update one saml provider config the button appears on the site login but dissapears from the other site from which it was visible before.
I tried having two sites on the same LMS container and on the same DB as well but I have the same issue only one site at a time can have the button visible on my configuration.
I will try to use the links you provided to create two completely separated devstack.