problem when xmlsec1 is not in system path

[Gijs Molenaar]

get_xmlsec_binary() in saml2/sigver.py looks for xmlsec1 installed in the system path. This fails when xmlsec1 is installed in a different location. It would be nice if this is configurable in some way.

[Lorenzo Gil Sanchez (lgs)]

You can set the xmlsec1 path in the configuration dict used in pysaml2.

Something like this:

SAML_CONFIG = {
    'xmlsec_binary': '/usr/bin/xmlsec1',
    # more stuff
}

[Gijs Molenaar (gijzelaar)]

Yes, you can set this, but it is not used in all cases.

get_xmlsec_binary() in saml2/sigver.py looks for xmlsec1 installed in the system path. This function is called to set XMLSEC_BINARY in sigver.py, so if you include sigver.py it fails.

[Roland Hedberg (roland-hedberg)]

So I've checked in a change to saml2/sigver.py that prevents the loading of sigver.py to fail if xmlsec1 is not within the system path. I also added a argument to get_xmlsec_binary(), to allow you to search in non-system paths.