shared link generates "No conversation state found in session for key"

Cantor, Scott cantor.2 at osu.edu
Fri Jan 20 16:55:23 EST 2017


On 1/20/17, 4:51 PM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:

> It's based on the the RemoteUser handler, with added support for isPassive and forceAuthn.  We got it from U-W.

You want to look at how it's handlng the conversation parameter. If the error occurs on the way back in, then it's been likely corrupted somehow, encoding or what not, and it's not lining up. It's sort of like a RelayState thing for the external mechanism.

-- Scott
    



More information about the users mailing list