root@sl-kilo-idp:~# curl -i -k \
> -H "Content-Type: application/json" \
> -d '
> {
> "auth": {
> "identity": {
> "methods": [
> "token"
> ],
> "token": {
> "id": "94e2a49d18604a88a5c157bda0e5ac5f"
> }
> },
> "scope": {
> "service_provider": {
> "id": "keystone-sp"
> }
> }
> }
> }' \
> https://keystone.idp/keystone/main/v3/auth/OS-FEDERATION/saml2
HTTP/1.1 500 Internal Server Error
Date: Wed, 04 Mar 2015 12:31:32 GMT
Server: Apache/2.2.22 (Ubuntu)
Vary: Accept-Encoding
Content-Length: 618
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
webmaster@localhost and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.2.22 (Ubuntu) Server at keystone.idp Port 443</address>
</body></html>
upon inspecting the function, the actual SAML response is fine at the controller level: https:/
seems to be a bug in wsgi.py, probably around here:
https:/