How to signing the request and send it to IdP

[Peter Schober]

* Tejash Mistry <Tejash.Mistry at FastTrackTeam.com> [2013-06-18 06:17]:
> I have tried <RelyingParty> node for sign request metadata. I have also
> tried  <CredentialResolver> node but my problem is still there.

You don't say what you did specifically. Or whether the setting had
any effect, i.e. whether the request then was signed (as per your log
files on DEBUG; you can always test the setting on a test SP of yours
to not disturb production).

> - Most of the federation are working fine but only one federation
> ask us to send sign request to them as their server is accepting
> only sign request.

How do "one federation" and "their server" (singular) go together?
If this is a Hub&Spoke-style federation, meaning you only interact
with a single SAML IdP, the suggested way to do that via a <RelyingParty>
element should work.
If it's a federation of many IdPs (and likely SPs) you'd need to add a
<RelyingParty> element for every relying party (i.e., every IDP) for
which this setting should be in effect.

AuthnRequest protocol messages are sent to IdPs, not "federations"
(unless these terms are homonymous in your case).

> - I have added <RelyingParty> node in the Shibboleth2.xml file and
> try to send a sign request metadata, but it was not working.

Sorry, "not working" is not an error description. Check your logs (as
indicated above) whether the setting makes any difference to outgoing
requests. If not, you're doing something wrong (you could supply your
config to sidestep more guesswork). If it does and the IdP is still
unhappy something else is off.

> - That federation asked us for Base64 encoded sign request metadata.

The software will generate requests according to the SAML specs.
-peter