Quoterequest for IdentityServer4 Skoruba Admin on Core 3.1 with external logins

I need to customize the .Net Core IdentityServer4 Skoruba Admin ( [login to view URL] ) with the following requeriments: - Skoruba admin using its own clientID "Skoruba Admin" and running localhost with port and extra "[login to view URL]" - Skoruba admin API using its own clientID "Skoruba AdminApi" and running localhost with port and extra "[login to view URL]" - Skoruba STS running localhost with port and extra "[login to view URL]" - Skoruba using SQLServer, not inmemory/MySQL/SQLLite or other provider - Working integration with Google, Facebook and AzureAD (in delivery TenantId, Domain and ClientId can have value replaced by "changeme") - Extended UserIdentity with FirstName, Lastname, LastLoggedIn and "LoginProvider" (if the login is from Google, Facebook, AzureAD o local Username/password, should be set on creation) - Working MVC Core 3.1 sampleproject with following functions - running on localhost with port and "[login to view URL]" - "using its own clientid "DemoMVC" - "home/privacy" demands auth an showing a list of claims for loggedin user - "home/ExtApi" get value from API on "[login to view URL]" - no local loginin, redirected to Skoruba IDS /login when auth is needed using "[login to view URL]" - Working Web API sample project utilizing OpenID Connect from the Identity Server - running on localhost with port and "[login to view URL]" - just one sample function, returning list of claims on loggedin user - "using its own clientid "DemoAPI" - Seeded data for all needed clients incl user: admin with Pa$$word123 (Uncommented line with easy understandable text) - SQL scripts for all tables creation and initial data (MSSQL) that is NOT covered by seed - All code changes must be commented and documented in a separate file (What file and line is added/changed) - All the MVC should have layoput as a MVC template located at [login to view URL] - The "product" (what I expect to receive) is the modified source codes, since it's meant to be used as a sample or base. - All the projects must work in two environments: local (development) and Windows Server 2019 with IIS/SQLServer (production). Optional - Instructions provided for Azure (nothing fancy, only understandable). - Removal of sensitive variables from configuration files. User Secrets to be used for local and Azure Key Vault for production. In your request please include the phrase "Banana Security", to avoid bots. Also the budget is higher than the stated level to avoid both bots and overprised. Quick delivery can get add-on tip. Regards Pelle