<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/11/2013 2:46 PM, Liam Hoekenga
wrote:<br>
</div>
<blockquote
cite="mid:CAH4ZtKQm8C_HztHRp9GkXY9AJ=4M16eqJdw1CZJ4_iqhRaz7uA@mail.gmail.com"
type="cite">
<div dir="ltr">Is it legal to have multiple AttributeEncoders of
the same type in a single AttributeDefinition?
<div><br>
</div>
<div>We're dealing with a vendor who expects<br>
<div><br>
</div>
<div><span style="font-family:arial,sans-serif;font-size:13px"> <resolver:AttributeEncoder
xsi:type="enc:SAML2String" name="email"
friendlyName="mail" /></span><br>
</div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">instead
of ..</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><font face="arial, sans-serif"><resolver:AttributeEncoder
xsi:type="enc:SAML2String"
name="urn:oid:0.9.2342.19200300.100.1.3"
friendlyName="mail" /></font><br>
</div>
<div>
<font face="arial, sans-serif"><br>
</font></div>
<div><font face="arial, sans-serif">Having two SAML2String
encoders in the definition /seems/ to work, so I'm mostly
wondering if it's *supposed* to work.</font></div>
<br>
</div>
</div>
</blockquote>
<br>
<font face="arial, sans-serif">I usually work around these by
defining a second attribute based on the first with the alternate
encoder, so it can be released independently.</font><br>
<pre class="moz-signature" cols="72">--
%% Christopher A. Bongaarts %% <a class="moz-txt-link-abbreviated" href="mailto:cab@umn.edu">cab@umn.edu</a> %%
%% OIT - Identity Management %% <a class="moz-txt-link-freetext" href="http://umn.edu/~cab">http://umn.edu/~cab</a> %%
%% University of Minnesota %% +1 (612) 625-1809 %%
</pre>
</body>
</html>