Mail attribute for Slack

[Corey Scholefield]

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.

I like the body of work here that reflects a “do and don’t” approach to adopting federated-services:

https://carmenwiki.osu.edu/display/CICIDM/The+CIC+Cloud+Services+Cookbook

Corey S.

[cid:image001.jpg at 01D39561.F6111F80]

Corey Scholefield
Team Lead, Identity Services
University Systems
University of Victoria<http://www.uvic.ca/>
T 250-472-4549
C 250-812-4861
coreys at uvic.ca
https://www.uvic.ca/systems



From: users <users-bounces at shibboleth.net> on behalf of Jeffrey Crawford <jeffreyc at ucsc.edu>
Reply-To: Shib Users <users at shibboleth.net>
Date: Wednesday, January 17, 2018 at 2:56 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Mail attribute for Slack

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.

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.

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.

Jeffrey E. Crawford
Enterprise Service Team
    ^         ^
   / \  ^    / \    ^
  /   \/ \  /   \  / \
 /        \/     \/   \
/                      \

You have been assigned this mountain to prove to others that it *can* be moved.

On Fri, Jan 12, 2018 at 4:12 PM, Michael Brogan <mbrogan at uw.edu<mailto:mbrogan at uw.edu>> wrote:
Upon re-reading the information from Slack (https://get.slack.help/hc/en-us/articles/205168057), it is the attribute Name, not the attribute FriendlyName they want customized.

For Name="urn:oid:0.9.2342.19200300.100.1.3" Slack wants Name="User.Email" [required]

For Name="urn:oid:0.9.2342.19200300.100.1.1" Slack wants Name="User.Username" [optional]

For Name="urn:oid:2.5.4.42" Slack wants Name="first_name" [optional]

For Name="urn:oid:2.5.4.4" Slack wants Name="last_name" [optional]

Just wanted to correct my mistake before this gets committed to the archives...

--Michael

-----Original Message-----
From: Michael Brogan
Sent: Friday, January 12, 2018 2:45 PM
To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: RE: Mail attribute for Slack

Thanks all for the responses. I guess we're stuck with creating non-standard attributes, like everyone else.

--Michael

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net<mailto:users-bounces at shibboleth.net>] On Behalf Of Cantor, Scott
Sent: Friday, January 12, 2018 10:20 AM
To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Re: Mail attribute for Slack
On 1/12/18, 1:07 PM, "users on behalf of Jim Fox" <users-bounces at shibboleth.net<mailto:users-bounces at shibboleth.net> on behalf of fox at washington.edu<mailto:fox at washington.edu>> wrote:

> I think Michael was wondering if the InCommon membership could
> sometimes stand united against this sort of thing.

I think Net+ was the only/obvious real vehicle for that within InCommon and they refused to given even that any teeth.

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.

But that's about it. We just don't operate together enough to exert leverage.

(And no, for the record, the Shibboleth Project isn't paying them, we don't use their commercial version.)

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180125/99bfdace/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 33777 bytes
Desc: image001.jpg
URL: <http://shibboleth.net/pipermail/users/attachments/20180125/99bfdace/attachment.jpg>