+xConfiguration can be updated dynamically if required. It's just that in many cases the configuration is known at startup time. You can set the configuration programmatically as demonstrated in our example projects. We do this at startup but there's no reason why you can't perform configuration updates as and when required. I welcome any other feedback you might have. Yeah we will certainly manage to handle and implement our case, we would just prefer it if it was more natively supported :) Let's say we do something like this: 1. Create a custom middleware and add this before mvc pipeline 2. By DI get SamlConfigurations and then make our own api request to external metadata url 3. Manually read metadata and set the corresponding properties for the first/specific PartnerIdentityConfiguration 4. This will then be used by any later middleware or saml requests triggered from mvc pipe It will work but we would prefer if it was more natively supported. Specifically if you could simply create/refresh/load a PartnerIdentityConfiguration from a specific url this would mean far less custom code for us. Thoughts?
|