Passing username & password (connection string) to EFCore at runtime

Asked Mar 08 '18 at 12:00

Active Mar 13 '18 at 18:03

Viewed 513 times

In a .Net Core 2.0 WebAPI. It is accessed internally by a few applications. However there is an expectation that each application will pass through the username & password to the Web API, that it will use to access the database, using EFCore 2.0.

When the Application makes a call to the API, it might be that there are a few queries that are ran during that connection. We want to make sure that the the context that is used for App1, isn't then the same one used by App2. We don't want the WebAPI to have to store usernames & passwords.

The Apps are Asp.Net Core 2.0 applications, as is the Web API.

App1 ---| 
App2 ---| --> WebAPI Endpoint --> EF --> DB.
App3 ---|

Is there a way of setting the WebAPI Startup to handle this scenario?

edited Mar 13 '18 at 18:03

bricelam

28,825
9
92
117

asked Mar 08 '18 at 12:00

David C

2,766
6
29
44

1

Don't pass username/passwords, pass OAuth authentication tokens from (for example) IdentityServer. – Gert Arnold Mar 08 '18 at 12:32
Thanks for that tip, any particular flow from Identity Server? – David C Mar 08 '18 at 15:20
What are the types of Apps? Mobile Client, Traditional Web Client, Windows Service? – aaronR Mar 08 '18 at 15:23
The Apps are traditional Asp.Net Core 2.0 (MVC) applications at the moment. @aaronR – David C Mar 08 '18 at 15:27
I think Implicit Flow unless you need refresh tokens then Hybrid. – aaronR Mar 08 '18 at 16:48

Passing username & password (connection string) to EFCore at runtime

0 Answers0