docusign failing

[Ted Fisher]

I got the 500 error corrected (tc config) and now I get this situation on our (2.4) idp:

I browse a URL to a docusign document which properly goes to my idp and authenticates and I get the doc.  Then from the same tab I go to the URL for a different docusign doc.  The docsusign SP sends me back to my idp with a new Authnrequest, which returns an empty response.

My idp-process.log includes: this after the authnrequest
      12:42:10.116 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:226] - Creating login context and transferring control to authentication engine
      12:42:10.122 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:181] - Storing LoginContext to StorageService partition loginContexts, key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXbf33ac4eea5f3331
      12:42:10.143 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:240] - Redirecting user to authentication engine at https://webapp.bgsu.edu:443/idp/AuthnEngine
      12:42:10.214 - TRACE [edu.internet2.middleware.shibboleth.idp.session.IdPSessionFilter:117] - Attempting to retrieve IdP session cookie.
      12:42:10.215 - TRACE [edu.internet2.middleware.shibboleth.idp.session.IdPSessionFilter:123] - Found IdP session cookie.
      12:42:10.216 - TRACE [edu.internet2.middleware.shibboleth.idp.session.IdPSessionFilter:81] - Updating IdP session activity time and adding session object to the request
      12:42:10.220 - TRACE [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:349] - Looking up LoginContext with key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXbf33ac4eea5f3331 from StorageService parition: loginContexts
      12:42:10.221 - TRACE [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:355] - Retrieved LoginContext with key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXbf33ac4eea5f3331 from StorageService parition: loginContexts
      12:42:10.318 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:588] - Unbinding LoginContext
      12:42:10.318 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:614] - Expiring LoginContext cookie
      12:42:10.322 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:625] - Removed LoginContext, with key XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXbf33ac4eea5f3331, from StorageService partition loginContexts
      12:42:10.325 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:178] - Incoming request contains a login context and indicates there was an error authenticating the principal, processing second leg of request

Any suggestions what is causing it to fail there?

BTW - our idp(s) redirect to CAS for each authn

Thanks.

Ted F. Fisher
-----Original Message-----

>     INFO: com.tc.exception.TCNonPortableObjectError:
>     Attempt to set the field of a shared object to an instance of a
> non-portable class. This
>     unshareable class has not been included for sharing in the configuration.

I don't know Terracotta, so I'm afraid there's nothing I can diagnose on that. Maybe others who used it might have an insight.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160510/d0ceef8f/attachment.html>