<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Can that not be done within a single attribute definition - that is, two encoders in the same attribute definition?<div>That seems to make what's being done a little more transparent, but is there a reason to avoid doing so?</div><div><br></div><div>David Bantz</div><div><br></div><div><div><div><div>On Thu, 27 Jun 2013, at 10:13 , Nate Klingenstein <<a href="mailto:ndk@internet2.edu">ndk@internet2.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">If you just want to release the same attribute data under a different SAML attribute name, then have a copy of the eppn definition with the AttributeEncoder changed to the new SAML name and an ID for the definition(eppnForSpecialSP or whatever).</span></blockquote></div><br></div></div></body></html>