Mail attribute for Slack

[Jim Fox]

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

Jim

> 
> > Is there any hope for not being subject to the whims of every vendor that comes along?
> 
>  
> 
> From what I’ve seen in this list and what I’ve heard speaking with other university IT staff, the only hope for not being subject to the whims of
> every vendor that comes along is to refuse to do business with them. If you’re big enough, then that financial threat may get them to budge. If
> you’re not, then at least you’re not doing business with a vendor that spits in the face of existing standards.
> 
>  
> 
> That being said, I understand fully that this is not always an option.
> 
>  
> 
>  
> 
> -Todd
> 
>  
> 
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Michael Brogan
> Sent: Friday, January 12, 2018 11:56 AM
> To: users at shibboleth.net
> Subject: Mail attribute for Slack
> 
>  
> 
> At the UW we’ve had a few Slack instances running with SSO and our IdP. Recently, for a new instance, we were told that the requirements have
> changed and that the IdP must release the mail attribute and that it must be asserted with a friendly name of “User.Email”.
> 
>  
> 
> We already release the mail attribute with a friendly name of “mail” but Slack said that wouldn’t work. When challenged about requiring new names
> for things that already have standard names, Slack said they would not change this requirement.
> 
>  
> 
> Have other campuses been told the same for recent Slack integrations? Any luck getting Slack to budge on this? Is there any hope for not being
> subject to the whims of every vendor that comes along?
> 
>  
> 
> Michael W. Brogan
> 
> Technical Lead, Identity and Access Management
> 
> UW-IT, University of Washington
> 
> 206-685-7521
> 
>  
> 
> 
>