You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using djangosaml2's dynamic configuration loading feature, and would like to be able to use something similar for djangosaml2idp. Is this a feature on the roadmap, or would you be open to pull requests?
Instead of hardcoding the idp settings in the config file, a callable is defined which returns a dictionary with the contents of SAML_IDP_CONFIG: SAML_IDP_CONFIG_LOADER = 'python.path.to.your.callable'
Thanks for the great package!
The text was updated successfully, but these errors were encountered:
I'm trying to come up with something similar. The main difficulty here resides in the ServiceProvider model which uses IDP.load() (more or less the config loading) but where the HttpRequest is not accessible (in djangosaml2 it is passed to the callable).
I'm going to bump this. We're in the process of trying to externalize all our configs on our IDP so we don't have to redeploy every time we want something to change. This would be nice feature to avoid that happening.
We're using djangosaml2's dynamic configuration loading feature, and would like to be able to use something similar for djangosaml2idp. Is this a feature on the roadmap, or would you be open to pull requests?
Instead of hardcoding the idp settings in the config file, a callable is defined which returns a dictionary with the contents of
SAML_IDP_CONFIG
:SAML_IDP_CONFIG_LOADER = 'python.path.to.your.callable'
Thanks for the great package!
The text was updated successfully, but these errors were encountered: