Shibboleth IdP integration with Oracle 11g Identity Federation

[Peter Schober]

* lalithj <j_lalith at hotmail.com> [2013-04-09 15:47]:
> Actually lot of our other SPs are HTTP redirect, feel like changing
> this(Oralce) to HTTP Post and see...

I was referring to the ACS URL binding
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST
by which the assertion is transported from the IdP to the SP.
(From this thread I was under the impression that errors only
happended after the authn was recieved by the IdP, but I may remember
that incorrectly.)

You're probably referring to how the authentication request is
transferred from the SP to the IdP (as HTTP-Redirect is not allowed
for that in the standard) which should be irrelevant for your
Artifacts error messsage.

Forget what I said if it only serves to confuse more.
I was just saying that if Artifacts are a problem, don't use them
(as both the IdP and the SP should find common bindings without
needing Artifacts).

Ask the vendor what the error means and how to circumvent it.
-peter