Hi,
I am trying to determine the best approach for configuring SAML for our particular situation. We have a multi-tenant SAAS application and want to allow any of the companies that have an account in our application to add their own SSO. We are using IdentityServer4 for authentication. As I see it, we need the configuration to be dynamic and loaded from the database. The changing of a companies SSO settings will occur in our main application and not on IdentityServer, so It seems therefore, that loading the configuration in the Startup.cs using services.Configure<> will not be suitable, as this will not necessarily have the latest information. What would the recommended approach to this be instead?
TIA
Dan
Hi Dan
Please take a look at our Configuration Guide.
You can programmatically set the configuration through the SAML configuration API. This can be done at startup or at any stage.
Alternatively, you can implement the ISamlConfigurationResolver interface and return configuration information as requested.
Both approaches are described in the guide.
[quote][/quote]
Hi Dan
Please take a look at our Configuration Guide.
You can programmatically set the configuration through the SAML configuration API. This can be done at startup or at any stage.
Alternatively, you can implement the ISamlConfigurationResolver interface and return configuration information as requested.
Both approaches are described in the guide.
Please take a look at our Configuration Guide.
You can programmatically set the configuration through the SAML configuration API. This can be done at startup or at any stage.
Alternatively, you can implement the ISamlConfigurationResolver interface and return configuration information as requested.
Both approaches are described in the guide.
Thanks for you response. I had started with implementing a custom ISamlConfigurationResolver. I will continue with that.
Dan
You’re welcome.