Why doesn't the WSDL from the WCF service turn on custom binding for STS?

Question

I am writing a WCF C # service that publishes an endpoint using WSHttpFederationBinding. We have our own security token server that provides tokens for which callers need to use user binding.

All this works fine for the C # client I wrote: it has its own binding in app.config like this:

<bindings>
  <customBinding>
    <binding name="CustBind">
      <security authenticationMode="UserNameForCertificate" requireDerivedKeys="true"
                messageProtectionOrder="SignBeforeEncryptAndEncryptSignature"
                requireSecurityContextCancellation="false"
                requireSignatureConfirmation="false">
        <secureConversationBootstrap/>
      </security>
      <httpTransport/>
    </binding>
  </customBinding>
  <wsFederationHttpBinding>
    <binding name="FedBind">
      <security>
        <message issuedTokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1"
                 negotiateServiceCredential="false">
          <issuer address="http://STSHost/MySTS" binding="customBinding"
                  bindingConfiguration="CustBind">
            <identity>
              <certificateReference x509FindType="FindBySubjectName" findValue="localhost"/>
            </identity>
          </issuer>
        </message>
      </security>
    </binding>
  </wsFederationHttpBinding>
</bindings>

However, I want users to be able to create their own clients in whatever language they need, simply considering that the WSDL publishes the WCF service. The problem is that when I try such a thing with the Developer Studio "Add Service" functionality, the resulting client does not work.

, , , app.config : STS "", . WSDL, , , .

WCF - WSDL ? app.config : "" , , . - , WCF, , WSDL?