I have a database that will be used by two different web applications. Solution A (user driven web application) resides on the public internet and will write / update / delete records to the db. Solution / Service B (not user but process driven) resides behind the FW and will only read the data from the db. For discussion purposes, let's just say that the db server will be set up in a way that it is accessible by both Solution A and B.
I'm trying to analyze what the best way is to set up the database server so that both applications A and B can interact in a secure way, but also be as loosely coupled to the database server as possible.
So far, I was thinking about creating 2 web API's on the database server. One would expose a read only interface for Solution B. And the other would be read write for Solution A. However, the question that comes to mind is how should I authenticate requests coming into the DB server from Solution A? If this db server is on the internal network, should I care since i "know" the users would have been authenticated when they hit the public facing server? If I do need to care, can I have solution A forward the JWT over to the internal db server? I think I would need to interact with the identity server from the DB server once again for the JWT to be of any value right?
Any comments or suggestions would be appreciated.