<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:monospace;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.im
{mso-style-name:im;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Times New Roman";
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Agreed. We are faced with a gigantic “educate the vendor” task in many respects. Sometimes you can get lucky, and catch them before they go sideways. Other times, not so much.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I like the body of work here that reflects a “do and don’t” approach to adopting federated-services:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://carmenwiki.osu.edu/display/CICIDM/The+CIC+Cloud+Services+Cookbook">https://carmenwiki.osu.edu/display/CICIDM/The+CIC+Cloud+Services+Cookbook</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Corey S.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:-5.4pt;border-collapse:collapse">
<tbody>
<tr>
<td width="92" valign="top" style="width:69.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><img border="0" width="125" height="133" id="_x0000_i1025" src="cid:image001.jpg@01D39561.F6111F80"></span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
</td>
<td width="396" valign="top" style="width:297.0pt;padding:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Corey Scholefield<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Team Lead, Identity Services<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">University Systems<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><a href="http://www.uvic.ca/"><span style="color:#0563C1">University of Victoria</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">T 250-472-4549<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">C 250-812-4861<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">coreys@uvic.ca<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">https://www.uvic.ca/systems<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">users <users-bounces@shibboleth.net> on behalf of Jeffrey Crawford <jeffreyc@ucsc.edu><br>
<b>Reply-To: </b>Shib Users <users@shibboleth.net><br>
<b>Date: </b>Wednesday, January 17, 2018 at 2:56 PM<br>
<b>To: </b>Shib Users <users@shibboleth.net><br>
<b>Subject: </b>Re: Mail attribute for Slack<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">I keep talking to admins at our campus, and the consensus is that vendors are actually getting worse as time goes on. If they wanted SAML integration they would download the Shibboleth SP and modify
their code to read it.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">Now vendors are implementing SAML their own way integrated in their application, and the short of it is, We keep having to do off the wall stuff that doesn't fit well with our current Shibboleth configuration
philosophy.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">This seems to be the opposite of what I would expect. Integrating used to actually be easier since Vendors would "rush" to support SAML and grabbed the easiest thing to allow that.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif"">Jeffrey E. Crawford<br>
Enterprise Service Team</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif""> ^ ^</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif""> / \ ^ / \ ^</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif""> / \/ \ / \ / \</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif""> / \/ \/ \</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif"">/ \</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"monospace","serif"">You have been assigned this mountain to prove to others that it *can* be moved.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jan 12, 2018 at 4:12 PM, Michael Brogan <<a href="mailto:mbrogan@uw.edu" target="_blank">mbrogan@uw.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt">Upon re-reading the information from Slack (<a href="https://get.slack.help/hc/en-us/articles/205168057" target="_blank">https://get.slack.help/hc/en-us/articles/205168057</a>), it is the attribute Name, not
the attribute FriendlyName they want customized.<br>
<br>
For Name="urn:oid:0.9.2342.19200300.100.1.3" Slack wants Name="User.Email" [required]<br>
<br>
For Name="urn:oid:0.9.2342.19200300.100.1.1" Slack wants Name="User.Username" [optional]<br>
<br>
For Name="urn:oid:2.5.4.42" Slack wants Name="first_name" [optional]<br>
<br>
For Name="urn:oid:2.5.4.4" Slack wants Name="last_name" [optional]<br>
<br>
Just wanted to correct my mistake before this gets committed to the archives...<br>
<span style="color:#888888"><br>
<span class="hoenzb">--Michael</span><br>
</span><br>
<span class="im">-----Original Message-----</span><br>
<span class="im">From: Michael Brogan</span><br>
<span class="im">Sent: Friday, January 12, 2018 2:45 PM</span><br>
<span class="im">To: Shib Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>></span><br>
<span class="im">Subject: RE: Mail attribute for Slack</span><br>
<br>
<span class="im">Thanks all for the responses. I guess we're stuck with creating non-standard attributes, like everyone else.</span><br>
<br>
<span class="im">--Michael</span><br>
<br>
<span class="im">-----Original Message-----</span><br>
<span class="im">From: users [mailto:<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a>] On Behalf Of Cantor, Scott</span><br>
<span class="im">Sent: Friday, January 12, 2018 10:20 AM</span><br>
<span class="im">To: Shib Users <<a href="mailto:users@shibboleth.net">users@shibboleth.net</a>></span><br>
<span class="im">Subject: Re: Mail attribute for Slack</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On 1/12/18, 1:07 PM, "users on behalf of Jim Fox" <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a> on behalf of
<a href="mailto:fox@washington.edu">fox@washington.edu</a>> wrote:<br>
<br>
> I think Michael was wondering if the InCommon membership could<br>
> sometimes stand united against this sort of thing.<br>
<br>
I think Net+ was the only/obvious real vehicle for that within InCommon and they refused to given even that any teeth.<br>
<br>
I think we at least have the advantage, whether it's through InCommon or just this list, to at least share knowledge of vendors engaging in such mistakes, so that we know about it (e.g., I could tell my boss if/when it ever comes up that I can't support Slack
because their implementation is not compliant) and perhaps head off purchasing decisions.<br>
<br>
But that's about it. We just don't operate together enough to exert leverage.<br>
<br>
(And no, for the record, the Shibboleth Project isn't paying them, we don't use their commercial version.)<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg" target="_blank">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a><br>
--<br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg" target="_blank">
https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>