<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Tue, 4 Mar 2014, at 08:14 , Christopher Bongaarts <<a href="mailto:cab@umn.edu">cab@umn.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;">You can work around it on the IdP side by defining additional attributes that encode to the proper names, and using attribute filters to selectively release either the wacky versions or proper versions depending on the SP.</span></blockquote></div><br><div>And this will of course allow you to migrate incrementally and somewhat gracefully to standard attribute naming.</div><div><br></div><div>My experience is that some services insist on their own “wacky” naming (or formatting) in any case, so encoding a single attribute to release with different names (or format) will be necessary anyway.</div><div><br></div><div>David Bantz</div></body></html>