IDP3 HTTP-Artifact form encoding

Wibke Börger boerger at luis.uni-hannover.de
Tue Oct 4 08:13:40 EDT 2016


Hello everyone,


we're using HTTP Artifact binding. The AuthnRequest is sent using 
HTTP-POST binding (to the idp/profile/SAML2/POST/SSO endpoint) and we 
would like to transmit the artifact form encoded via POST, too. However, 
the artifact is always URL-encoded and sent via GET.

Is there a way to change this behaviour so that the artifact will be put 
in a form and sent via POST?

Is the choice of artifact message encoding determined by some parameters 
in the request or metadata that I might be overlooking?

(We're using Identity Provider 3.2.1)


Thanks,
Wibke

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4968 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://shibboleth.net/pipermail/users/attachments/20161004/5fbe8fbc/attachment.p7s>


More information about the users mailing list