Thank you so much Scott.<br><br>I just realized that my question is also related to another recently asked question, whose title is:<br> "<font><span>Multiple Username/Password login handlers</span></font>" <br>
asked by Clay Cooper.<br><br>In that email, there is a concrete example.<br><br>Anyways, this requires a lot more configurations than option (2), I will continue with option (2).<br><br>Thanks,<br>Yaowen<br>
<br><br><div class="gmail_quote">On Thu, Aug 16, 2012 at 5:17 PM, 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">
<div>On 8/16/12 7:58 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>> wrote:<br>
><br>
>No. What I said was that you have to use different context classes to<br>
>indicate which handler you want. That doesn't mean using the same context<br>
>class, it means using different ones. You have to make up the two classes<br>
>to use.<br>
<br>
</div>I think your confusion is that you think the only allowable context<br>
classes are the ones defined by the standard which are technology signals<br>
like "password". That isn't limited, you can define any context class you<br>
want by creating a URI for it and defining the meaning. The only thing<br>
connecting the built-in "password" class and the UsernamePassword handler<br>
in the IdP is you putting the string into the file. Pick your own URIs and<br>
you can do anything you want with them.<br>
<div><div><br>
-- Scott<br>
<br>
--<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>
</div></div></blockquote></div><br>