Does samlify supports using AssertionConsumerServiceIndex instead of ProtocolBinding and AssertionConsumerServiceURL?

[honhaochen]

Part of my SP's metadata is as follow:

<md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</md:NameIDFormat>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://---1/sso" index="0"/>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://---2/sso" index="1"/>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://---3/sso" index="2"/>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://---4/sso" index="3"/>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://---5/sso" index="4"/>
        <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://---6/sso" index="5"/>

if I would like to use one of the index (e.g. 5), I should be able to specify them via AssertionConsumerServiceIndex="5" in the Authn Request, but does samlify allows such configuration?

[stjeffrey]

I need this as well but it seems Samlify doesn't support this. If I can manage to write something within the library I'll do a pull request.

[stjeffrey]

I wrote a PR that should allow this to work #532