net.shibboleth.idp.authn.ExternalAuthenticationException: No conversation key found in request

Cantor, Scott cantor.2 at osu.edu
Sun Mar 22 16:39:03 EDT 2015


On 3/22/15, 4:15 PM, "Kathy E. Wright" <kewrig at clemson.edu> wrote:

>directly does successfully redirect to our external SSO but I haven't figured out how to make this the default from the doc instructions.  

The protected path should be /idp/Authn/RemoteUser, same as in V2. How you protect that is not in scope of our documentation. That URL will include parameters, so your system has to ensure that if the user is redirected somewhere else to login, that the URL they come back to includes the parameters.

>When I test authentication with an SP I am redirected to the IdP's internal login web service so I know I've missed some steps in my set-up.

I don't know what "internal login web service" you're referring to, you mean the example login form?

Using the RemoteUser method alone primarily requires changing the idp.authn.flows property from "Password" to "RemoteUser". If "Password" isn't included in the property expression, there's no way for the form to be appearing.

-- Scott



More information about the users mailing list