# SingleSignOnService Binding HTTP-POST **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [June 4, 2018, 6:25pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474 "2018-06-04T18:25:27Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![everson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/everson/32/31907_2.png) [@everson](https://discuss.elastic.co/u/everson)\ **Post date:** [June 4, 2018, 6:25pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/1 "2018-06-04T18:25:28Z")
Hi! We are configuring x-pack to integrates with an SSO provider, but unfortunately, this SSO Service exposes only HTTP-POST binding. I saw on X-Pack documentation that it only supports Redirect binding but I would want to know if anyone had this problem and how to solved that. ---
**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\ **Post date:** [June 5, 2018, 1:40am UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/2 "2018-06-05T01:40:30Z")
Our SAML integration only supports HTTP-Redirect to the IdP (it does support HTTP-Post on return from the Idp to Kibana), and I don't think you'll be able to work around that. What IdP do you have that only supports HTTP-Post? If this is an issue for you, and you have a support or sales contact, then please ask them to raise an Enhancement Request to support HTTP-Post (and include details about the IdP). ---
**Author:** ![everson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/everson/32/31907_2.png) [@everson](https://discuss.elastic.co/u/everson)\ **Post date:** [June 5, 2018, 2:09pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/3 "2018-06-05T14:09:18Z")
Hi Tim! Thanks for your answer. The IdP is provided to us by our customer and had developed by themselves. Only for clarification purposes, is a recommendation (best practice) that the IdP needs to support HTTP-Redirect binding? ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [June 5, 2018, 4:14pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/4 "2018-06-05T16:14:09Z")
Hi Everson, It is actually more than a recommendation: [Conformance Requirements for theOASIS Security Assertion Markup Language (SAML) V2.0](http://docs.oasis-open.org/security/saml/v2.0/saml-conformance-2.0-os.pdf), page 9, all Identity Providers `MUST` support the `HTTP-Redirect` binding. Furthermore, the use of `HTTP-Redirect` binding is preferred in pretty much all interoperability profiles published, i.e.: saml2int (now driven by Kantara) [in progress version here](https://kantarainitiative.github.io/SAMLprofiles/saml2int.html), [current version here](https://saml2int.org/profile/current/) ---
**Author:** ![everson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/everson/32/31907_2.png) [@everson](https://discuss.elastic.co/u/everson)\ **Post date:** [June 5, 2018, 4:27pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/5 "2018-06-05T16:27:55Z")
Thanks for your answer! It was very enlightening. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 3, 2018, 4:27pm UTC](https://discuss.elastic.co/t/singlesignonservice-binding-http-post/134474/6 "2018-07-03T16:27:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.