<div dir="ltr">This is the scenario: <div><br></div><div>The user logs in using an email address. We have a problem with special characters in email addresses in our LDAP server so we want to translate transparently the email address to another field, such as uid. This will be done by changing the JAAS context with the associated uid and use it in the actual LDAP bind.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 April 2014 15:39, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 4/23/14, 3:12 AM, "Vasile Alin" <<a href="mailto:alinachegalati@gmail.com">alinachegalati@gmail.com</a>> wrote:<br>
<br>
>We need it just before the actual login process. With this LDAP call<br>
>we'll change the principal login username inside the context.<br>
<br>
Why would you do that? The only advantage of using LDAP for<br>
authentication, which is *not* its purpose, is to do a search + bind to<br>
indrect the username. The module can already do that.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br>
</blockquote></div><br></div>