Under Community Review

This would require some changes to a number of areas to allow the schema name qualifier, as well as testing with the layered permission approach. We will continue to review the interest in this for a future release.

using common mcroservices account for all microservices

we got few microservices installed (discovery, content and delivery service) with oracle as database.

Creation of DB script does create new schemas for each microservice which is fine. 

we can use schema name and its password to access each microservice which is working.

but we wanted to have common account created in oracle with password but will have access to all the schemas (select, insert, delete update) roles. Schema will have higher privileges like drop tables which belong to it.

The idea is to use one common user (****MS).

but in the configuration file , we don't have an option of adding commonusername/password.

if we use common user/password instead of schema/password, it does not work. The reason being once connected, microservices need to know which schema it needs to connect to. 

So is it possible to have application code change to schema (which is being passed as parameter in config file) , 

Application code needs changing something like 

if schema1 is specified in config xml (as new element)

ALTER SESSION SET CURRENT_SCHEMA=SCHEMA1

if schema2 is specified in config xml (as new element)

ALTER SESSION SET CURRENT_SCHEMA=SCHEMA2

if schema3 is specified in config xml (as new element)

ALTER SESSION SET CURRENT_SCHEMA=SCHEMA3