#195 Traceback in SOAP logout raising exception
Closed: Fixed None Opened 6 years ago by rcritten.

Trying to log out of Shibboleth after doing logout, restart apache, logout and got this traceback from Ipsilon:

HTTP Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/cherrypy/_cprequest.py", line 670, in respond
    response.body = self.handler()
  File "/usr/lib/python2.7/site-packages/cherrypy/lib/encoding.py", line 217, in __call__
    self.body = self.oldhandler(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/cherrypy/_cpdispatch.py", line 61, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/site-packages/ipsilon/util/page.py", line 91, in __call__
    return op(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ipsilon/providers/common.py", line 90, in root
    return op(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ipsilon/providers/saml2idp.py", line 143, in GET
  File "/usr/lib/python2.7/site-packages/ipsilon/providers/saml2/logout.py", line 303, in logout
    message = self._soap_logout(logout)
  File "/usr/lib/python2.7/site-packages/ipsilon/providers/saml2/logout.py", line 202, in _soap_logout
    raise InvalidRequest('SOAP HTTP error code', response.status_code)
TypeError: __init__() takes exactly 2 arguments (3 given)

Not exactly sure what the reproducer is/was. I had logged in, then clicked logout. I was seeing issues, which I assume were on the Shibboleth end, where I had to do a refresh to log back in. So I was doing a lot of shift-reload at the time, even on the logout page.

I was also experimenting with stripping down some of the default configuration. I had just removed the discovery protocol information from the <SSO> object in shibboleth2.xml and restarted apache and shibd, went back to the browser and clicked logout and I got this traceback.

Fields changed

milestone: => 1.2

Fields changed

owner: => rcritten
status: new => accepted

master: 0779639

resolution: => fixed
status: accepted => closed

Metadata Update from @rcritten:
- Issue assigned to rcritten
- Issue set to the milestone: 1.2

5 years ago

Login to comment on this ticket.