<div dir="ltr">Hi David<div><br></div><div>Yes, although that is not the main issue I believe, if we take an LDAP server as an example it would be simple to login the user programatically by calling the Unsolicited SSO with the required parameters. The issue would be that since the login was done programatically on server side, the user browser never sets any cookie which, to my understanding, is required by Shibboleth (Though it may be a misconception on my part and is only required for the default UserPassword loginhandler).</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 25 July 2013 15:30, David Langenberg <span dir="ltr"><<a href="mailto:davel@uchicago.edu" target="_blank">davel@uchicago.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Sounds like what you need to do is build a custom LoginHandler that handles the user-registration / initial authentication part. <div><br></div><div>Dave</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div class="h5">
On Thu, Jul 25, 2013 at 7:25 AM, Byte Flinger <span dir="ltr"><<a href="mailto:byteflinger@gmail.com" target="_blank">byteflinger@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div dir="ltr">Hi<div><br></div><div>I am trying to test the following scenarion:</div><div><br></div><div>1 - User fills some information about himself and submits a form</div><div>2 - An action is triggered which creates an user on backend server LDAP (on IDP side) and redirect the user back to the SP</div>
<div>3 - Once redirected to the SP, the user will be automatically logged in without having to fill the information he just did.</div><div><br></div><div>The idea is to trigger a login request to Shibboleth together with the user creation on LDAP by programatically calling Unsolicited SSO with the required information however I am uncertain how to handle the part where the user is automatically logged in once he is redirected to the SP.</div>
<div><br></div><div>I could redirect the SAML Response gotten from the login request all the way back to the SP (Via the user browser) however if I understand correctly, once that happens the SP will just redirect to Shibboleth and because the user browser will not have the session cookie set, Shibboleth will once again ask for a login.</div>
<div><br></div><div>I am guessing that if the SP uses that SAML Response when redirecting to Shibboleth, Shibboleth will notice the user is already logged in, set the necessary cookies and redirect back to SP, however that sounds like a lot of unnecessary back and forth.</div>
<div><br></div><div>Are there any suggestions on a better of going about this? I am guessing the cookie is required for recognizing the user as logged in?</div></div>
<br></div></div><span class="HOEnZb"><font color="#888888">--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br>
<br clear="all"><div><br></div>-- <br>David Langenberg<div>Identity & Access Management</div>
<div>The University of Chicago</div>
</font></span></div>
<br>--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br></blockquote></div><br></div>