Well looking at what was written... hopefully this is crazy in a good way. If it's not... well, this is the last bit I'll write without The technical part that's uncertain has to do with authentication, authorization, identity, and access management. The .NET Framework Web API application is a classic monolith that uses self signed certificates and custom OWIN identity objects. In speaking with my

The .NET Core environment we use for all current projects has a separate identity server which supports different flows including Oauth 2 implicit, password resets, etc.

WE can't disclose the identity and access management code but it could be offered as a "free" service to Sql Server Saturday or other causes

So it seems to makes we would want to build an engineering mule to develop the application logic and .NET Core API without consideration of actual identity infrastructure. If this is done the right way then the whole thing could be done "open source" in public I guess.

As bumbling as this is and without a full plan I guess it me flailing around trying this out. Why? 1) it's an interesting project, 2) there's a need for something to help out SQL post PASS, 3) demonstrate my data access project/app dev framework, and 4) I guess get referrals for consulting business (obliquely). To shake the tree and see what people will contribute. My big fear tho is nobody cares or it's not well received.