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
Currently the satosa-saml-metadata script creates a metadata file called backend.xml, or, when creating split metadata files, filenames that include an index number:
So, when one starts to use --split-backend (or --split-frontend), this will cause a change in the generated filenames, which can be problematic as other system might rely on them (aggregator tools etc).
The script could have some options to influence the output file names. Some ideas:
An option to override the name of the first file
Include the name of the backend/frontend in the file name
The text was updated successfully, but these errors were encountered:
I am planning to do a rewrite but it is not very high on my list.
The idea is to switch to poetry, use typer, rework the plugin loader and routing and then simplify how the options are set and add options to specify output names/patterns/strategies.
Currently the
satosa-saml-metadata
script creates a metadata file calledbackend.xml
, or, when creating split metadata files, filenames that include an index number:SATOSA/src/satosa/scripts/satosa_saml_metadata.py
Line 23 in c629dd5
So, when one starts to use
--split-backend
(or--split-frontend
), this will cause a change in the generated filenames, which can be problematic as other system might rely on them (aggregator tools etc).The script could have some options to influence the output file names. Some ideas:
name
of the backend/frontend in the file nameThe text was updated successfully, but these errors were encountered: