<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Scott,<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>You are the man! All fixed.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Mel</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="font-size: 14px;" class=""><font color="#007236" class=""><b class="">Melvin Lasky</b><br class="">Associate Director of Enterprise Architecture</font><br class=""><br class=""></span></div><span><img apple-inline="yes" id="E24754EA-D774-4574-A05F-56A7E2436F72" src="cid:30040C3B-58F3-41D0-91CF-B57E6B6E2FB7@manhattan.edu" class=""></span><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="font-size: 14px;" class=""><br class=""><br class=""><br class="">Riverdale, NY 10471<br class="">Phone: 718-862-7410<br class=""><a href="mailto:melvin.lasky@manhattan.edu" class="">melvin.lasky@manhattan.edu</a><br class="">www.manhattan.edu</span><br class=""><br class=""></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jun 3, 2022, at 2:04 PM, Cantor, Scott <<a href="mailto:cantor.2@osu.edu" class="">cantor.2@osu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">You don't do this by touching anything but metadata. Add the relevant NameIDFormat to the SP's metadata or add a filter to add it. Done.<br class=""><br class="">Do NOT create one-off NameID generator beans and do not use activation conditions to control them. Just because it's possible doesn't mean you should ever do it. It's there as an absolute last resort.<br class=""><br class="">The documentation does not in any way suggest doing this, so I don't know why people are doing it or what would lead somebody to think it makes sense, but it's analagous to creating an LDAP plugin that changes what attribute values are served up for a fixed attribute type based on the bind DN. Nobody would even think of doing that, and this is the same.<br class=""><br class="">If you create an email Format generator based on the filtered value of mail (or whatever attribute you use), then you need not worry about anything but releasing the relevant attribute to the SP and making sure its metadata stipulates the right Format.<br class=""><br class="">-- Scott<br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>