
lv6c8 (lv6c8) asked a question.
So here is my problem. I have a situation where a customer wants to have 3 or more individual working environments of an API and a client application. They use multiple databases which means they require 3 separate instances of the API running. In terms of authentication to clients/third part access, this is handled by Identity Server, which supplies a JWT to access data. There's a bit more such as permissions but let's stick with the simple idea that they are secured by JWT produced by calling ID Server endpoints in the usual fashion.
The question here is, should we have one STS that manages the three same API's (different server for each) or have three instances of the STS for each API deployment? Bare in mind that these are all for the same customer and the very same API but connected to different versions of the same database, i.e. PRODUCTION, TEST, VALIDATION.
My own understanding is that you should only ever have one ID Server, thoughts?

Hello Martin!
Thank you for raising the case with Okta. Cristian here with the Support Team.
In regard to your question, there is no one-side-fits-all answer to whether you should have one or three instances of the Server. It depends on the specific needs and constraints of your customer's project.
In order to make an informed decision that align with your customer's objectives, resources and security requirements, please take into consideration the bellow factors:
Best regards,
Cristian Lazar
Okta Global Customer Care