Develop Merge: Pre Connect-a-thon 26

[JoeShook]

• A new Udap.Proxy.Server example that turns your FHIR server into a UDAP enabled FHIR server.
• The Udap.Proxy.Server is the new https://fhirlabs.net/fhir/r4 fhir server endpoint. The backing FHIR server is a Google Cloud HealthCare FHIR Server.
• A new Udap.Smart.Metadata package for some experimenting I am doing with SMART. May add SMART on FHIR to my auth server going forward. Just not sure yet how I handle letting the Auth Server know about the launch parameter ahead of time. Back channel or Proxy Server or redirect dance?
• Refreshed the Udap.Auth.Server to support /authorize? errors accorging to rfc 6749. The server is back to passing all of the https://www.udap.org/UDAPTestTool/ server tests. Actually Test 16 is failing becuase the test tools is reusing the jti parameter for reated registrations thus triggering a replay block at Udap.Auth.Server. A bug has been filed and it will be fixed.
• TouchStone tests are also in good shape.
• I started to experiment with hosting UdapEd in a Maui Application. I have a lot of the UdapEd blazor app hosted inside of the Maui App and working. Windows and Android tested. Android does not auto discover intermediate certificates, so there would be a choice to make. Either add code to get the intermediary or as a convension always install the intermediary on the device just like you would do with the trust anchor certificate. The idea of this experiment is to go through the mechanics of building a CSR from a device, assuming that every instance of a device would need it's own client certificate. Last thing to note about UdapEd it that it is now hosted in a new repository to keep the Maui bits for compilation from slowing down this repo. See JoeShook/UdapEd
• The Maui experiment led to another technology I have been wanting to apply. It is called the RCL or Razor Class Library. You can take all your Razor Pages, Javascript and static content and centralize it in a project. This allows you to publish it as a NuGet packages. This worked good for centralizing the Blazor components that could then be shared with Blazor and Maui for the UdapEd project. But even better, now there is a Udap.Server.Ui package that contains all the Razor pages for the Udap.Auth.Server. Those pages are nothing more than the Duende example pages with a few UDAP specific pages. But the idea of packaging this up so you can just include it in your UDAP Auth Server is a nice feature that removes post manual configuration. It would be cool to rewrite all of these pages as Blazor Components with MudBlazor. Volunteers?