SP: sending HTML form template to client

[Satheesh Kumar]

Hi Team,
     I need your thoughts on below IDP's behavior,
     We have SP 2.6 and when sending <authnrequest> to one of our
registered IDP, the attributes like "TARGET", "RelayState", "SAMLRequest",
"SAMLResponse", "SAMLart", "SigAlg"  are encoded within a form as hidden
fields in "bindingTemplate.html" and the form is submitted along with authn
request. This is happening only for specific IDP's and I am not sure why
this is happening.
     In Shib shar log I can spot this difference -
      IDP 1  sends attributes in hiddden form
DEBUG OpenSAML.MessageEncoder.SAML2POST : message encoded, *sending* *HTML
form template to client*
DEBUG Shibboleth.Listener : dispatching message
*(new_shib/Login::run::SAML2SI)*

      IDP 2  sends attributes in browser post
DEBUG OpenSAML.MessageEncoder.SAML2Redirect : message encoded, *sending
redirect to client*
DEBUG Shibboleth.Listener : dispatching message *(new_shib/SAML2/POST)*

      So let me know my guess is correct,

   -     In IDP 1 the SSO attributes are encoded within a hidden form and
   it is sent to the corresponding IDP via POST.
   -     In IDP 2 the SSO attributes are sent via POST headers.

 So what makes the SP to behave in this way ??

Thanks in advance,
Satheesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170911/9de62c4a/attachment.html>