[Bug or Question] Request from disco always have context.path Saml2 instead of other backend NAME

[peppelinux]

Introduction

Probably this issues is a bug related to SaToSa, I coded a workaround as a microservice here:
#220

Explaination

When I select an IDP from DiscoServ (pyFF), for example

https://satosa.testunical.it:10000/Saml2/disco?entityID=http://idpspid.testunical.it:8088

SaToSa tell me

[urn:uuid:919bfe04-a291-4ce3-979c-1d9317177057] Found registered endpoint: module name:'Saml2', endpoint: Saml2/metadata

Expected Behavior

I've registered another Saml2 backed called spidSaml2, in its metadata I can read

<ns2:DiscoveryResponse Binding="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol" Location="https://satosa.testunical.it:10000/spidSaml2/disco" index="1"/>

My question is the following:
a) Is this a bug and the microservice I developed is just a temporary workaroud

or

b) all the request coming from Disco (context.path = $backendname/disco) will have always the Saml2 backed as default?

If b) the microservice coul be usefull, probably with a additional code refactor, if a) can you confirm this please?

[peppelinux]

Any hints, ideas, suggestions?
Could it be related to #230 ?

I'd like to have a feedback on this if possible, I'll really appreciate, thank you

[peppelinux]

Nowadays we have decide backend by target microservice and also idphinting microservice to do this kind of routing