wcf tradition http surrogate authentication

is illusory yield wcf tradition surrogate castle tradition credentials?

i've found answer smoke-stack : , nonetheless i've got complication, use i'm authenticating opposing uses the possess authentication, i've got twin sets certification (one by proxy, justify opposing service)

i'm controlling technique described answers doubt yield use credentials. e.g.

client.clientcredentials.username.username = username;
client.clientcredentials.username.password = password;

i set castle surrogate controlling something this:

(client.endpoint.binding wshttpbinding).proxyaddress = ...;

how i set effectively twin sets credentials? (nb: certification surrogate tangible use different!) also note surrogate sum indispensably default component surrogate details.