<div dir="auto">DSpace also has the same procedure. Hope we can also follow the same</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 21, 2018, 17:02 Yuri <<a href="mailto:yurj@alfa.it">yurj@alfa.it</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just replace old user account with the new one on the user table.<br>
<br>
<br>
Il 21/08/2018 13:13, Stoynova, Zaharina ha scritto:<br>
><br>
> Hi all,<br>
><br>
> we have the following task: our Eprints archive exists and there are <br>
> around 600 User accounts in it. Till now we have always used the local <br>
> login and in the next 3-4 months we would like make it possible that <br>
> our users authenticate only with Shibboleth. For all new users the <br>
> authentication workflow is clear but for all users which have already <br>
> account in our archive we have to find a mechanism that will make it <br>
> possible for them to login with Shibboleth and to keep their Working <br>
> Area and Publications in their accounts. Therefore after a successful <br>
> first Shibboleth login we have to “map” their old user-id and their <br>
> Shibboleth ID. We have planned the following workflow:<br>
><br>
> 1.Login with Shibboleth<br>
><br>
> 2.If this user with Shibboleth ID is already in our database then <br>
> grant access to the Archive<br>
><br>
> 3.Otherwise ask whether the user has a local account<br>
><br>
> a.If the answer is no then create a new account<br>
><br>
> b.If the answer is yes then the user has to authenticate with his <br>
> local account (username AND password)<br>
><br>
> i.If the local authentication is successful replace the local ID, <br>
> email and name and keep a link to the local id (for further reference)<br>
><br>
> ii.If the local authentication is not successful go to 3.<br>
><br>
> Has someone better suggestions? Has someone already “mapped” local <br>
> against Shibboleth accounts?<br>
><br>
> Thank you very much in advance!<br>
><br>
> Best Regards,<br>
><br>
> Zaharina Stoynova<br>
><br>
><br>
><br>
> *** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
> *** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
> *** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
> *** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer noreferrer" target="_blank">http://forum.eprints.org/</a><br>
<br>
<br>
*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" rel="noreferrer noreferrer" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a href="http://www.eprints.org/tech.php/" rel="noreferrer noreferrer" target="_blank">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a href="http://wiki.eprints.org/" rel="noreferrer noreferrer" target="_blank">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a href="http://forum.eprints.org/" rel="noreferrer noreferrer" target="_blank">http://forum.eprints.org/</a><br>
</blockquote></div>